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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description goes beyond that with genuinely non-obvious behavior: the last page is undeletable and deleting the home page promotes the next one. It still omits recoverability and permission requirements, but the added rules are real value.

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, zero filler, with the primary action stated first and the edge cases immediately after. Every clause earns its place.

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 no output schema, the description covers the cascade (content is deleted) and the two surprising edge cases an agent must not discover by accident. Missing only permission/authorization expectations and irreversibility, which would make it fully self-contained.

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% and both parameters (id, pageId) are documented with examples in the schema, so the baseline is 3. The description adds nothing about the site-id vs page-id distinction or how the pair is interpreted.

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 ("Delete a page") and clarifies scope by noting it removes the page's content too, which distinguishes it from delete_node, delete_collection, and delete_site. It stops short of explicitly naming a sibling, but the resource is unambiguous enough that an agent can route correctly.

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?

Usage is implied by the obvious delete-a-page semantics, with no explicit statement of when to prefer delete_node or update_page alternatives. The two business rules given are constraints rather than selection guidance, and no prerequisites (permissions, auth) are mentioned.

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