delete_saved_search

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

Discloses destructive nature with qualifier 'low-risk', clarifies what is deleted and what is not (items/citations), and explains idempotency replay semantics. This adds valuable context beyond the annotations' destructiveHint and idempotentHint flags.

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 sentences are efficiently packed with critical safety information, usage contrasts, and parameter explanation. Front-loaded with 'DESTRUCTIVE, but low-risk' to immediately alert the agent.

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 lack of output schema and minimal schema descriptions, the description provides sufficient context: what it deletes, what it doesn't affect, idempotency behavior, and alternatives. Complete for a simple deletion tool.

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 has 0% description coverage, but the description compensates well for idempotency_key, explaining its opaque string nature and replay behavior. The 'key' parameter is not explicitly described, though its purpose as the saved search identifier is implied from context.

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 'permanently deletes this saved search definition', using a specific verb and resource. It also distinguishes from sibling tools by noting it doesn't touch items or citations, unlike delete_item_permanently/delete_collection.

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 provides when-to-use guidance by contrasting with delete_item_permanently/delete_collection, explaining that a saved search is just a stored filter, not a container. It also explains idempotency_key behavior, directing to delete_item_permanently's docstring for full details.

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