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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds a non-obvious side effect—'Does not count toward your monthly searches'—which is not captured in annotations. This extra detail helps an agent understand the impact beyond the basic safety profile.

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 description consists of three short, purposeful sentences: the action, the prerequisite, and a relevant side-effect. No redundant or filler content is present, making it highly concise and well-structured.

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?

For a simple delete tool with one parameter, no output schema, and strong annotations, the description covers the necessary steps (how to get the ID, the action, and a side-effect). It is sufficiently complete, though it could optionally mention that deletion is permanent, but that is already implied by destructiveHint.

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 has 100% description coverage for the single 'id' parameter, explaining it comes from list_saved_searches. The description repeats this same guidance without adding new semantics, so it provides no additional meaning beyond the schema.

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 action ('Delete a saved search by ID') with a specific verb and resource, distinguishing it from sibling tools like list_saved_searches, save_search, and update_saved_search. It also specifies the scope (by ID) and directs the user to list_saved_searches first, reinforcing the intended purpose.

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?

It provides an explicit prerequisite: 'Use list_saved_searches first to find the ID.' This gives clear workflow guidance. While it doesn't mention alternatives, no other delete tool exists among siblings, so the guidance is sufficient for correct usage.

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