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

The annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds substantial context beyond them: what is actually deleted (releases, source, channels, connectors, drains, mailboxes), what survives (detached resources, sessions, memories), the irreversibility, the protected architect agent, and the no-op answer for a missing name. These are exactly the traits an agent needs before calling a destructive tool.

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 crucial facts are front-loaded ('Permanently destroy... This cannot be undone, so confirm with the user first'), and nearly every sentence carries non-redundant information. It is a single dense paragraph, though, which is heavier to parse than a bulleted when-to-use / what-gets-destroyed structure would be.

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?

Given a destructive tool with no output schema, the description covers all parameters, the consequences for each kind, ordering prerequisites, edge cases (nonexistent name, protected architect agent), and even the return implication ('the answer names them for destroy_resource'). Nothing an agent needs to invoke this safely is missing.

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 the schema itself already documents kind, name, org_name, and site_token, including the kind-refusal behavior and the name/site_token exclusivity. The description mostly restates these, only adding the rationale that a publisher can always take their own site down; so the baseline of 3 is appropriate rather than a value-add.

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?

Opens with a specific verb and resource ('Permanently destroy a website, app, or agent and stop serving it'), and it clearly separates itself from sibling destroyers (destroy_resource, destroy_session, destroy_memory, destroy_channel, destroy_connector) by enumerating exactly what this tool removes versus what the others handle. An agent can distinguish it from every sibling without opening a schema.

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 explicit when-to-use and ordering guidance: 'confirm with the user first', 'call destroy_session and destroy_memory first if they should go', and the exclusion 'the architect agent cannot be destroyed'. It also names the alternative tools (destroy_resource, destroy_session, destroy_memory) and the conditions that select them.

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