redmine_delete_message

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

The description adds two behavioral traits: deletion is permanent, and the tool honors the REDMINE_MCP_READ_ONLY flag. However, it does not disclose side effects (e.g., cascade deletion of replies), permission requirements, or error states. Since no annotations are provided, the description carries the full burden, and it partially fulfills it.

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 with two sentences and a line, no fluff. It could benefit from a slightly more structured format (e.g., bullet points for key facts), but overall it is efficiently written and front-loaded with the primary action.

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 simple operation (one required param, output schema present), the description is minimally complete. It covers permanence and read-only mode, but omits details like error handling, permission requirements, or the impact on related entities. For such a straightforward tool, it is adequate but not thorough.

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 only parameter is message_id (integer). Schema coverage is 0%, and the description does not elaborate on its meaning, format, or constraints. The parameter name is self-explanatory, but the description should at least confirm that it refers to the ID of the forum message to delete.

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 explicitly states 'Delete a forum message' with the qualifier 'Permanent,' clearly indicating the action and resource. It distinguishes from sibling tools like redmine_create_message or redmine_reply_message, which serve different purposes.

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?

No explicit guidance on when to use this tool versus alternatives. While the tool name implies deletion, the description lacks context such as prerequisites, alternative approaches (e.g., using redmine_delete_issue for issues), or conditions under which deletion is appropriate.

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