delete_page

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

With no annotations provided, the description carries the full burden; it does disclose the critical behavioral trait of irreversibility, which is exactly what an agent needs before a destructive call. However, it says nothing about required permissions, whether the page must exist, what happens to child pages, or the response shape.

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?

Fifteen words, front-loaded with the action and its permanence, then the parameter hint. Zero filler and nothing an agent can misread.

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?

A one-parameter destructive tool with no annotations and no output schema; the description covers the essential facts (what it does, that it is permanent, where the ID comes from). Missing permission/cascade details keep it short of a 5.

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?

Single parameter at 0% schema description coverage, so the description must compensate. It does identify page_id's provenance (obtained from list_pages), which adds real meaning; it does not specify the ID format, but that gap is minor for one string parameter.

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?

Specific verb ('Delete') plus resource ('a page') with an explicit permanence modifier ('for good'). It clearly differs from siblings like update_page or create_page, and the irreversibility is stated up front.

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 parenthetical '(page_id from list_pages)' routes the agent to the discovery sibling before calling, and 'Cannot be undone' implies when-not-to-use without spelling out a softer alternative such as update_page. No explicit exclusion statement, but context is clear.

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