Delete website

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

The description goes well beyond annotations by explaining the async deletion process, the immediate transition to a deleting state, and background removal of server resources. It also reinforces the destructiveHint with 'permanently deletes,' and is consistent with the idempotentHint.

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 concise sentences with no filler. The core action and permanence are stated first, followed by the important asynchronous behavior.

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 single-parameter destructive operation, the description is complete: what it deletes, permanence, and the asynchronous lifecycle are all covered. No output schema exists, but none is needed for correct invocation.

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% and the parameter is already described as 'Agency Plan website UID.' The description adds no additional parameter detail, but with full schema coverage, the baseline of 3 is appropriate.

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 states a specific verb ('permanently deletes') and a specific resource ('Agency Plan website'), making the tool's scope clear. It does not explicitly contrast with sibling hosting_deleteWebsiteV1, but the 'Agency Plan' qualifier provides enough differentiation.

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?

The description clearly indicates this tool is for Agency Plan websites, which gives the agent context for selecting it. It does not explicitly state 'use this instead of hosting_deleteWebsiteV1' or list exclusions, so it falls short of a 5.

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