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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds value the annotations cannot: the delete cascades to the backing file, deleting the home page promotes the next page, and the last page is blocked. Those are exactly the side effects and failure modes an agent needs before firing a destructive call.

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 short sentences with zero filler; the destructive scope is front-loaded and the two edge cases follow. Every clause carries information that changes agent 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 destructive tool with destructiveHint declared and no output schema, the description covers scope, cascade, and the two blocked cases. Only the site-vs-page id relationship is left unaddressed, which is a minor gap against a fully documented schema.

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 description coverage is 100%, so both `id` (site id) and `pageId` are documented in-schema, and the 3 baseline applies. The description adds nothing about whether pageId is scoped per site or global, which is the one genuine ambiguity left given the optional site id.

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?

"Delete a page and its file" gives a specific verb plus resource and even names the cascade (the file goes too). It is clearly distinguishable from delete_site, delete_component, and delete_collection_row by resource. There's no explicit sibling callout, but the resource noun does the disambiguating work.

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 supplies one real "when not to use" condition (the last page can't be deleted) and notes the home-page special case. It does not point at alternatives such as unpublish_site or update_page for the cases where deletion is the wrong move, so guidance is implied rather than spelled out.

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