tool_stop_fare_watch

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

No annotations provided, so description carries full burden. It discloses writes to local profile store, no external auth, returns updated watch record, and explains consequences of pausing vs deleting (keeps history, stops checking; permanent removal, no recovery).

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?

Well-structured and front-loaded: first sentence states purpose, then details. Every sentence adds value with no fluff.

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 low schema coverage, no annotations, and no output schema, the description is complete. It explains behavior, parameters, and usage. Return value is mentioned ('Returns the updated watch record').

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 description coverage is 0%, but description adds meaning: watch_id comes from tool_list_fare_watches or tool_watch_fare; delete false=pause (reversible), true=delete permanently. This compensates for low schema coverage.

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 'Pause or permanently delete a fare watch by its ID.' It uses specific verbs (pause/delete) and a specific resource (fare watch), and distinguishes from sibling tools like tool_check_fare_watches and tool_list_fare_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?

Explicitly says when to use: 'Use this when the user has booked the flight or no longer needs the alert.' Also provides alternatives: 'Use tool_list_fare_watches to find the watch_id if unknown. Use tool_check_fare_watches to re-price before deciding to stop.'

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