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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond them by enumerating the cascade of destroyed entities (searches, baselines, change events, feed links) and by stating what survives the operation. That scope-of-destruction detail is exactly the context an agent needs before triggering an irreversible delete.

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?

Three sentences, front-loaded with the destructive action and its cascade, then the intent requirement, then the exclusions. No sentence is redundant or padding.

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?

With an output schema present, return values need no explanation, and the zero-parameter schema leaves nothing else to document. The description covers the two things that matter for a destructive, no-argument tool: exactly what is destroyed and exactly what is not.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to add or omit. The description correctly spends its words on scope rather than inventing inputs.

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 precise verb ('permanently delete') and a precisely scoped resource ('the authenticated private saved-search workspace and all its searches, baselines, change events and feed links'). This clearly distinguishes it from the sibling delete_saved_search, which removes a single search rather than the whole workspace.

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?

Gives an explicit precondition ('Requires explicit user intent to delete the entire workspace') and three negative boundaries (does not delete the login account, public records, or another workspace). It stops short of naming delete_saved_search as the narrower alternative for deleting one search instead of the workspace.

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