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

Adds substantial context beyond the destructiveHint annotation: soft delete semantics, immediate disappearance from the dashboard and list_sites, article publishing stops, subscription cancels at end of billing period with comped sites deactivated at once. It also discloses irreversibility from the API and the two-phase confirmToken handshake.

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?

A single dense paragraph that leads with what is destroyed and follows with permissions, partner behavior, and the confirmation flow. Every clause carries information, though the subscription/comped-site detail could be tightened slightly.

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 no output schema, the description still explains what the first call returns (a summary and confirmToken) and what state results after confirmation. For a destructive, non-idempotent operation, nothing an agent needs to call it 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 baseline is 3, but the description adds real workflow meaning: the first call with no confirmToken returns a summary and token, and the second call proceeds. That is more than a restatement of the schema's confirmToken text and clarifies the required call sequence.

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 specific verb and resource ("Removes a site from the account") and immediately scopes the meaning of removal as a soft delete that removes it from list_sites. This separates it cleanly from delete_article, delete_product, and the other delete_* siblings.

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 clear preconditions (only the site owner; invited teammates cannot; white-label partners may delete a client's site) and the escape hatch for reversal (contact support). It does not name an alternative tool for the non-owner case, so it stops just short of explicit when-not-and-use-instead routing.

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