redmine_attachment_download

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

With no annotations, the description carries the transparency burden and discloses meaningful behavior: HTTP method, response format (base64 and content_type), and the REDMINE_MAX_DOWNLOAD_BYTES size cap. It does not mention auth, error handling, or cap-overflow behavior, but the disclosed details are substantive.

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 two tight sentences with no filler. The core action is front-loaded, and every clause adds useful information: endpoint, response format, and size limit.

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 one-parameter GET operation, the description covers purpose, method, response shape, and a hard limit, which is largely sufficient to call the tool. The remaining gaps are authentication details and explicit positioning relative to redmine_attachment_get.

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 coverage is 0% and there is one required id parameter. The description does not directly define id as the attachment ID, but the /attachments/download/:id endpoint makes this inferable. This is acceptable for a single simple integer parameter but does not fully compensate for the missing schema description.

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 states the specific action ('Download attachment binary') and gives the exact GET endpoint, making the tool's purpose clear. It is distinguishable from attachment upload/update/delete siblings, though it does not explicitly contrast itself with redmine_attachment_get.

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 use case is implied: use this when you need the raw attachment binary or its base64 representation. The description does not name alternatives like redmine_attachment_get or provide explicit when-to-use / when-not-to-use guidance.

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