redmine_add_attachments

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state that files are uploaded and automatically attached, which names the key side effect, but it omits permission requirements, failure behavior, and whether the operation is reversible.

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?

Two short sentences with no filler: the first establishes action and target, the second clarifies the upload-and-attach behavior. The information is front-loaded and 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?

For a simple two-parameter tool with complete schema descriptions, the essential invocation details are present. However, the lack of an output schema means return/confirmation behavior is not addressed, and the relationship to sibling redmine_upload_file is not clarified.

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 explains both issue_id and file_paths adequately; the description adds only the 'one or more' count notion. No extra constraints like file size or allowed types are given, but this is acceptable at the schema-coverage baseline.

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 uses a specific verb ('Add') and resource ('one or more file attachments to an existing Redmine issue'), stating exactly what the tool does. It is clearly distinguishable from sibling redmine_upload_file by the attachment-to-issue target.

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 makes the core use case clear—attaching files to an existing issue—so an agent can infer when to use it. However, it does not explicitly contrast with redmine_upload_file or mention when to prefer one over the other, leaving some selection ambiguity.

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