delete_page_tool

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

With no annotations provided, the description carries the full disclosure burden. It successfully identifies the admin authentication requirement and acknowledges a return value ('Deletion result'), but omits critical behavioral details like whether deletion is permanent, if history is preserved, or what specific result structure is returned.

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 uses a structured docstring format (Args/Returns) that is front-loaded with the essential action and constraint. It is appropriately concise, though 'Deletion result' is minimally descriptive (acceptable given the existence of an output schema).

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 has only 2 simple parameters and an output schema exists (per context signals), the description provides sufficient context. The auth requirement is the critical contextual piece for a deletion operation, though additional notes on permanence would achieve 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?

Schema description coverage is 0%, meaning no parameter descriptions exist in the structured schema. The description fully compensates by documenting both 'title' ('Page title to delete') and 'reason' ('Reason for deletion (default: empty)') with clear semantics and default value information.

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 opening sentence 'Delete a wiki page' provides a specific verb and resource. It distinguishes from siblings like edit_page_tool or move_page_tool by explicitly stating 'Requires admin authentication,' signaling this is a privileged operation compared to standard editing tools.

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 phrase 'Requires admin authentication' provides clear prerequisite guidance on when to use (and implicitly when not to use) the tool. However, it lacks explicit guidance on alternatives such as move_page_tool for renaming vs. deletion, or warnings about permanent data loss.

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