redmine_add_note

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

With no annotations, the description carries the burden. It indicates a write operation ('Add') and provides communication style guidance, but it does not disclose potential side effects like status changes via optional params or any permissions/notifications. It is adequate but not rich.

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 three concise sentences: purpose, use cases, style guide. It is front-loaded with the primary action and has no wasteful content. Every sentence earns its place.

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 schema fully covers parameters and the tool is a note-adding mutation, the description is fairly complete for the task. It could be improved by mentioning alternatives like redmine_update_issue for field changes, but overall it provides sufficient context for selection and 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 100%, so the schema already documents all parameters in detail. The description adds no extra parameter meaning beyond the schema; it only references style guidelines for the 'notes' parameter, which the schema already covers.

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 'Add a comment/note to an existing Redmine issue' with a specific verb and resource, and lists example use cases. However, it does not explicitly differentiate from sibling tools like redmine_update_issue or redmine_edit_journal, so it lacks overt sibling distinction.

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 says this is 'the primary way to post updates, progress reports, investigation findings, or review feedback,' which gives clear contextual use. But it does not explicitly state when not to use it or mention alternatives, so there are no exclusions.

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