delete-page

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

The description discloses soft delete behavior (page & history remain), return value, and failure conditions. Annotations already provide destructiveHint: true, but description adds recovery context beyond annotations.

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?

Three sentences, front-loaded with primary action, no wasted words. Efficient and clear.

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?

Given destructive and idempotent annotations, plus soft delete disclosure and failure conditions, the description is complete for a tool with 2 params and no output 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 coverage is 100% with descriptions for both parameters (title, comment). The description doesn't add new parameter-level information; baseline 3 is appropriate.

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 tool removes a wiki page from public view and returns the deleted title. It distinguishes from sibling tools like undelete-page by noting it's a soft delete.

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 informs that this is a soft delete, can be restored with undelete-page, and fails if page doesn't exist or user lacks permission. It implies not for permanent deletion, but doesn't explicitly compare to other write tools like update-page.

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