redmine_add_comment

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

No annotations are provided, so the description carries full burden. It discloses critical behaviors: honors REDMINE_MCP_READ_ONLY (safety constraint), direct PUT method, no pre-fetch or workflow check, and details about note handling (empty rejection, newline literal requirement, Markdown rendering) and private permission requirements.

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 well-structured with a header and bullet-like Args section. While it is moderately long, every sentence adds value and there is no redundancy. Minor verbosity could be trimmed, but overall efficient.

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 presence of an output schema (implied by context signals) and the sibling tool list, the description provides sufficient context for an agent to select and use the tool. It covers the action, parameter semantics, and behavioral traits. Missing information on error handling or response format, but that is likely in the output schema.

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%, but the description fully compensates by explaining each parameter: issue_id (numeric), note (constraints on empty, newline literal, Markdown), and private (boolean with permission note). This adds significant meaning beyond the bare 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: 'Append a comment (journal entry) to an existing issue.' It uses a specific verb ('append') and resource ('comment to an existing issue'), distinguishing it from siblings such as redmine_update_journal or redmine_close_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 does not explicitly provide when-to-use or when-not-to-use guidance relative to alternatives. However, the context signals list many sibling tools, and the description mentions honoring REDMINE_MCP_READ_ONLY and being a direct PUT, which implies it is for simple comment addition without status changes. No explicit exclusions or alternative suggestions are provided.

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