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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no statement about whether deletion is permanent or soft, whether restore_site can undo it, what permissions are required, or what happens to dependent resources.

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 single sentence is short but not concise in the useful sense — it is under-specified rather than economical, carrying zero information beyond the title. There is nothing to front-load because nothing is said.

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 destructive single-parameter tool, the description omits the one thing annotations cannot convey: whether the deletion is recoverable and via which sibling (restore_site, list_deleted_sites). The presence of restore_site makes that context highly relevant and its absence a real gap.

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?

Only one parameter ('id') with 100% schema description coverage, so the schema fully documents the input. The description adds no meaning about the identifier (e.g., that it must be an existing, non-deleted site), so the baseline of 3 applies.

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 is a verbatim restatement of the tool name and title ('Delete a site'), adding no scope, target, or distinction from the 30+ siblings. It is more informative than 'Process' but still tautological, and it never clarifies what a 'site' is here or how this differs from delete_site_template or delete_proxy.

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?

No guidance on when to use this tool versus alternatives. The sibling list contains restore_site and list_deleted_sites, which strongly imply deletion may be recoverable and that a restore path exists, yet neither is referenced. The agent must infer all routing decisions.

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