Upload Redmine Attachment

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

Beyond the mutation implied by readOnlyHint=false, the description discloses a concrete side effect: 'Attaching adds an entry to the issue history'. It also warns about Redmine's file size limit and that the limit is reported. These are useful behavioral traits not present in annotations.

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: a one-line purpose, a bulleted source choice, an Args list, and two behavioral notes. Every sentence adds useful information without redundancy or fluff.

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 tool with six parameters and conditional constraints, the description covers all necessary invocation details: required fields, mutual exclusion, filename defaults, optional parameters, side effects, and error behavior around file size. No output schema exists, but none is needed for correct usage.

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 100%, but the description adds critical logic missing from the schema: exactly one of file_path or content_b64 must be provided, filename is required with content_b64, and filename defaults to the basename of file_path. This significantly clarifies how to invoke the tool correctly.

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 opens with 'Attach a file or image to a Redmine issue', a specific verb-resource statement. It also distinguishes itself from the sibling redmine_add_note by noting that attaching already adds an entry to issue history, so no separate note call is needed.

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 explicitly says 'there is no need to call redmine_add_note separately', giving a clear when-not to use an alternative. It also sets usage expectations with 'Give exactly one source' and the file size caveat, though it does not discuss usage versus the download attachment sibling.

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