add_to_watchlist

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it adds a threshold but doesn't disclose whether this mutates state, requires any auth, what happens on duplicate card additions, whether this persists across sessions, or what the output schema returns. For a state-mutating operation with zero annotation coverage, this is a significant gap.

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?

The single-sentence description is extremely concise, but it's under-specified rather than genuinely concise. It conveys the bare minimum of purpose with no structure or elaboration. Short is good, but this borders on too little information for a 6-parameter tool.

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?

This is a mutating tool (adds to watchlist) with no annotations, 6 parameters at 0% schema coverage, and an output schema. The description entirely fails to explain parameter semantics, expected behavior on duplicates, or the return value. Given the complexity (6 params, required fields) and zero supporting structure, the description is inadequate.

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%, so the description must compensate, but it doesn't explain any parameters. The description adds no meaning to card_id, price_source, variant, direction, target_price, or note. The 'manual price threshold' phrase hints at target_price and direction but doesn't explain allowed values (e.g., what 'below'/'above' means) or how price_source should be specified.

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 'Add a manual price threshold to the local watchlist' has a clear verb (add) and resource (watchlist), and mentions it's adding a manual price threshold. It distinguishes somewhat from siblings like remove_from_watchlist and list_watchlist, but doesn't clarify how it differs from check_watchlist or the broader watchlist concept.

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?

No guidance is provided on when to use this tool vs alternatives. It doesn't explain when a manual threshold is needed vs automatic price tracking, nor does it distinguish from sibling tools like check_watchlist. There is no exclusionary or alternative-naming guidance.

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