admin_delete_wiki

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

With no annotations, the description carries full burden. It discloses the destructive nature and the confirmation requirement, but lacks details about irreversibility, cascading effects (e.g., on attachments), or authorization needs. The confirmation is a behavioral trait, but more context would improve transparency for a deletion operation.

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 is extremely concise with two short sentences, each conveying essential information. Every word serves a purpose, and the structure is clear and front-loaded.

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 simple delete operation with full schema coverage and no output schema, the description is adequately complete. It names the action, resource, and a key usage constraint. However, a note about irreversibility or permissions would make it more robust, but not strictly necessary for a basic tool.

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%, so baseline is 3. The description adds 'MUST confirm' which is redundant with the schema description of the 'confirmed' parameter ('Must be true'). No additional semantic value beyond the schema is provided.

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 ('DELETE') and the resource ('a wiki page'), providing a specific verb-resource pair. It distinguishes from sibling delete tools by naming the resource, and the sibling tool list includes other delete operations for different resources, so there is no ambiguity.

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 includes a requirement ('The user MUST confirm'), which guides usage, but it does not specify when to use this tool versus alternatives (e.g., archiving or updating). No context about prerequisites or conditions is provided.

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