delete_wiki_page

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly mentions the cascading deletion of sub-pages per Redmine's default behavior, which is a critical side effect. However, it does not mention permissions, irreversibility, or error handling, leaving some behavioral aspects undisclosed.

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 concise and front-loaded with the main purpose, followed by a compact argument list. Every sentence earns its place; there is no redundant or fluff content.

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 two parameters, the description covers the most important nuance (sub-page deletion). An output schema exists, so return values are not the description's job. Minor gaps around permissions and reversibility exist, but they do not block correct invocation.

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%, so the description must compensate. It only restates the parameter names with minimal elaboration ('project identifier', 'title of the page to delete') without adding format constraints, examples, or usage nuances. This adds little beyond the raw schema.

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 target (wiki page), and pertinently notes the sub-pages behavior. This distinguishes it from sibling tools like list_wiki_pages, get_wiki_page, and create_or_update_wiki_page, which cover other operations on the same resource.

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 makes it obvious when to use this tool: when you need to delete a wiki page. It does not explicitly mention exclusions or alternatives, but the context of the tool name and sibling list provides clear usage context. Lacking a 'when not to use' statement, but not misleading.

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