hyperd.watch.cancel

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses the ops fee, x402 auth path, and 404 vs 403 behavior to prevent side-channel leaks. However, it does not mention the success response or any other side effects beyond cancellation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with front-loaded purpose. No extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers main purpose, fee, auth, and error behavior. Lacks description of success response or return value, but the tool is simple and no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear description for watch_id. The tool description adds no additional meaning beyond what the schema already provides for the only parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it cancels a watch owned by the user. Verb 'cancel' plus resource 'a watch you own' distinguishes it from sibling tools like create and list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (cancel a watch you own) and includes context on the fee and auth path, but does not provide explicit when-not-to-use or comparisons to alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.