watchlist_remove

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real value beyond that: 'verify the remaining order' discloses post-write confirmation behavior, and 'Refuses a missing entry' discloses failure semantics — useful traits not captured by annotations.

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 tight sentences; the action and its guardrail ('Refuses a missing entry') are front-loaded with no wasted text.

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?

No output schema and a destructive tool, yet the description covers the action, the read-back verification, and the missing-entry refusal. Nearly complete; could note idempotency (re-removal behavior) but the annotations cover the main safety signals.

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 83%, so the schema already documents almost every parameter in detail. The description only restates that the entry must be exact and the watchlist is identified by ID, adding little beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (remove) and resource (one stored entry from a named watchlist), and the word 'one' implicitly distinguishes it from the sibling watchlist_remove_bulk. Clear, though it doesn't explicitly name the sibling it excludes.

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?

The context of removing a single entry vs bulk is implied by 'one exact stored entry', and 'Refuses a missing entry' tells the agent an edge case, but there's no explicit guidance on when to prefer watchlist_remove_bulk or watchlist_set_entries.

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