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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description earns credit by disclosing what actually gets destroyed (the collected mentions, not just the search config) and that the operation is irreversible and requires user confirmation — context the boolean hints cannot express.

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 short clauses: the action plus its cascade effect first, then the irreversibility and confirmation warning. No filler, and the most consequential information (mentions are destroyed, cannot be undone) is front-loaded.

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 3-parameter mutation tool with full schema coverage, complete annotations and no output schema, the description covers everything an agent needs: what is removed, that it is irreversible, the required confirmation step, and the source of the id.

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 100%, so workspaceId and idempotencyKey are already self-documenting and the baseline would be 3. The description adds value by telling the agent where the required id comes from (list_saved_searches), which the schema's generic id text ('Required for pause, resume and delete') does not provide.

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 pairs a specific verb (delete) with a specific resource (saved search) and adds scope the name alone doesn't convey: the mentions it found are deleted too. It also disambiguates from siblings like list_saved_searches, pause_saved_search and resume_saved_search, which operate on the same object without destroying it.

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 gives clear operational context: this cannot be undone and the agent should confirm with the user first, which is exactly the right gate for a destructive action. It does not explicitly name a non-destructive alternative (pause_saved_search) for the case where the user only wants to stop listening temporarily, so the when-not guidance is implied rather than stated.

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