delete-page

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

With no annotations, the description carries the burden. It discloses that deletion is permanent and requires admin/sysop rights. Yet it does not detail any further side effects (e.g., impact on history or associated files) or whether the deletion is reversible via undelete-page, making it only partially transparent.

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?

The description consists of two concise sentences: the first states the action, and the second states the permission requirement. Every word is necessary, making it highly efficient.

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 the tool's destructive nature and lack of annotations, the description should provide more context about expected outcomes. While the permission and permanence are mentioned, there is no guidance on success/failure responses or broader consequences. The moderate complexity and complete schema coverage balance this, resulting in a mid-range score.

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?

All four parameters have schema descriptions (100% coverage), so the baseline is 3. The tool description itself adds no extra parameter context, thus the score remains at 3.

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 states 'Delete a wiki page permanently.' This is a specific verb (delete) and resource (wiki page), and the word 'permanently' distinguishes it from undelete-page. Clear and unambiguous.

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 notes 'This requires admin/sysop rights on the wiki,' which is a prerequisite for usage. However, it does not explicitly explain when to use this tool versus alternatives like undelete-page or page editing, leaving the decision to inference.

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