jira_download_attachment

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

No annotations are provided, so the description carries full burden. It only says 'Download' without explaining what happens to the file (saved? returned as bytes?), side effects, authentication needs, or error behavior. The schema implies saving to a filename, but the description doesn't affirm this behavior.

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 sentences, with the first stating the core action and the second providing a necessary prerequisite. No fluff or repetition; every word 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?

The tool is simple, but with no output schema and no annotations, the description should clarify what the agent receives after download (e.g., file path, binary content). It also omits error or overwrite behavior. However, it provides a useful workflow hint (use fetch_issue first), making it minimally complete.

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%: both parameters have descriptive entries ('Filename to save the attachment as' and 'Attachment ID from the issue's attachments list'). The description adds no additional parameter meaning, so baseline 3 applies.

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 'Download a single Jira attachment by its ID,' which is a specific verb and resource with a scoping qualifier ('single'). It clearly distinguishes this from siblings by focusing on downloading attachments, which no other sibling tool does.

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 instructs 'Use jira_fetch_issue first to get attachment IDs and filenames,' establishing a clear prerequisite and workflow context. It does not mention exclusions or alternatives, but given the sibling list has no other download tool, this is sufficient.

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