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

Annotations already indicate destructive and non-readonly, but the description adds detailed behavioral context: immediate soft-delete, freed hostname, pending purge, and response fields (accepted, purgesAt). Fully discloses what happens beyond annotations.

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 with no filler, efficient and front-loaded with the core action and key constraints. Every sentence earns its place.

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?

Covers the deletion flow, immediate and long-term effects, and response fields. For a soft-delete tool with an output schema (mentioned), this is sufficiently complete for an agent to use 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?

Schema coverage is only 33% (confirm has description). The description explains confirm=true is required and its role, but does not explain name or siteId. It adds value for confirm but leaves other params undocumented, partially compensating for low coverage.

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 it is a soft-delete for a site, describes immediate effects (hostname freed, stops serving) and eventual purge. It distinguishes from other deletion tools like delete_source_file by specifying it's for the entire site.

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 says 'Use this for the normal remove this from my dashboard flow', providing clear context for when to use this tool. Though it doesn't mention alternatives, the sibling list includes many tools, and the usage context is well-defined.

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