Preview a site deletion

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing what the inspection surfaces (associated domains, databases, FTP accounts, root directory), which is the tool's actual payload since no output schema exists. It stops short of noting permission requirements or that a preview does not guarantee the deletion will succeed.

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 compact sentences with zero filler; the purpose/output enumeration comes first and the mandatory ordering call-out second. The opening nominal fragment is slightly indirect but still front-loads the meaning efficiently.

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 a single required parameter, full schema coverage, and no output schema, the description carries the burden of explaining what is returned and does so by listing the blast-radius components. Adding the pre-condition that the id must reference an existing site would make it fully complete.

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 exists at 100% schema coverage, and the schema already documents it as 'Website id to inspect.' The description does not add format, constraints, or lookup guidance beyond this, 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?

States a specific verb+resource (preview what a site deletion would remove) and enumerates the affected resources: domains, databases, FTP accounts, root directory. It is clearly distinguished from the sibling site_delete, which performs the actual removal.

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 states the condition and ordering: 'Always call this before site_delete so the user can see the blast radius.' The alternative (site_delete) is named and the relationship between the two is unambiguous.

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