Redmine MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes an issue, implying a destructive mutation, but lacks critical details: it doesn't specify if deletion is permanent/reversible, what permissions are required, if there are side effects (e.g., cascading deletions), or what the response looks like (e.g., success/failure indicators). For a destructive tool, this is a significant gap in transparency.

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 a single, direct sentence with zero wasted words. It front-loads the key action ('Delete') and resource, making it immediately understandable. Every part of the sentence earns its place by specifying the tool's core function efficiently.

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 complexity (destructive mutation with no annotations and no output schema), the description is incomplete. It lacks behavioral details like permanence, permissions, or response format, and doesn't compensate for the absence of annotations or output schema. This leaves the agent with insufficient context for safe and effective use.

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?

The input schema has 100% description coverage, with the single parameter 'issue_id' fully documented in the schema. The description adds no additional parameter semantics beyond implying the ID is for deletion, which is already clear from the schema. This meets the baseline of 3 for high schema coverage, but no extra value 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 resource ('a Redmine issue/ticket by ID'), making the purpose unambiguous. It distinguishes from siblings like 'create_issue' or 'update_issue' by specifying deletion. However, it doesn't explicitly mention that this is a destructive operation beyond the verb 'Delete', which slightly limits differentiation from non-destructive siblings like 'get_issue'.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing issue existence or permissions), exclusions (e.g., not for bulk deletion), or direct alternatives (e.g., 'update_issue' to close instead). This leaves the agent with minimal context for tool selection.

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