delete-page

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

The description fully discloses behavioral traits: soft delete (data remains in DB), restoration possibility via undelete-page, and failure conditions. This aligns with annotations (destructiveHint=true, idempotentHint=true) and adds value beyond them.

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: first states primary action and return, second explains soft delete and failure conditions. No wasted words, front-loaded with key information.

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?

The description is complete for a deletion tool with no output schema: it covers behavior, return value, failure modes, and references sibling tool for restoration. Annotations further supplement safety awareness.

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?

With 100% schema description coverage, the baseline is 3. The description adds context about the return value (deleted title) and slight nuance for 'comment' (reason). It doesn't repeat schema info, providing marginal extra value.

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 clearly states the action (removes a page from public view), the resource (wiki page), and the return value (deleted title). It distinguishes itself from the sibling undelete-page by specifying soft delete behavior.

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 provides clear conditions for use (page exists, user has permission) and hints at alternatives via undelete-page. It could be more explicit about when not to use this tool, but the soft delete context implies restoration possibilities.

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