cancel_watch

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

With no annotations, the description fully discloses behavior: watch is marked cancelled (not deleted), return format on success, and implication of being able to retrieve cancelled watches. This goes beyond minimal disclosure.

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?

All sentences are valuable, front-loaded with core action, then examples, return format, and additional guidance. No waste.

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?

Given the simple tool with 1 param and no annotations, the description covers purpose, usage, behavior, parameter meaning, and return format comprehensively. Output schema is described in-line.

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?

The single parameter watch_id is explained beyond the schema: it is the ID from watch_flight_price or list_active_watches. Since schema coverage is 0%, the description compensates fully.

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?

The description clearly states the tool cancels a flight price watch by watch_id, with specific verb and resource. It distinguishes from siblings like watch_flight_price and list_active_watches.

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?

Provides explicit usage scenarios (e.g., 'stop watching that route'), tells when to use list_active_watches first, and clarifies that cancelled watches are not deleted and can be listed with include_cancelled=true.

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