redmine_delete_wiki_page

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

The description discloses key behavioral traits: the deletion is permanent ('Permanently delete'), there is no soft-delete in Redmine, it honors the REDMINE_MCP_READ_ONLY environment variable, and it specifies the return format on success and failure. Since no annotations are provided, the description fully covers the behavioral burden.

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 action. It uses only three short sentences plus a parameter list, with no extraneous information. Every sentence serves a purpose.

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 that the output schema exists (per context signals) and the tool is a straightforward delete operation, the description covers all necessary aspects: action, parameters, return values, and safety behavior. No additional information is needed.

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?

With 0% schema description coverage, the description adds meaningful context: 'numeric id or identifier slug' for project and 'wiki page title' for title. While brief, it provides enough information beyond the bare schema types to guide the agent.

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 'Permanently delete a wiki page (and all its historical versions)', specifying the verb (delete), resource (wiki page), and scope (including history), which distinguishes it from sibling tools like redmine_create_wiki_page or redmine_get_wiki_page.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or comparisons with other delete tools among siblings.

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