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

Beyond the destructive and idempotent hints, the description details permanent removal, no archive, webhook deletion, impact on already-delivered postings, and the non-error behavior when deleting a nonexistent slug. This is rich behavioral context that annotations alone do not convey.

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?

Although lengthy, the description is well-structured and every paragraph earns its place for a destructive operation. The key action is front-loaded, followed by parameter clarification, irreversible consequences, usage warnings, and return semantics.

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?

The description covers what happens, what cannot be undone, how to avoid misuse, what is returned, and how the action relates to sibling tools. With an output schema and detailed annotations present, nothing essential is missing for an agent to call this correctly.

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 schema already fully documents the single parameter, including the slug-vs-display-name distinction. The description repeats this same point and adds surrounding context, but it does not add new parameter-level meaning beyond what the schema provides.

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 states a specific action and resource: 'Delete a saved search and its delivery, permanently.' This clearly distinguishes it from save_search and list_saved_searches, and the title reinforces the same meaning without adding ambiguity.

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 description explicitly warns 'Do NOT use it to pause' and explains the correct alternative: letting a plan lapse pauses saved searches. It also notes that re-creating a deleted search requires calling save_search again with the filter, giving an agent clear decision rules.

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