jira_download_attachment

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

Discloses the core behavior (downloads, saves to temp file, returns path), which is sufficient given no annotations. However, lacks details on side effects like temp file lifetime, required permissions, or whether it is a read-only operation.

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?

A single, efficient sentence that front-loads the verb and resource. No unnecessary words.

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?

Adequate for a simple tool with one parameter, covering the main action and output. However, lacks context on prerequisites (e.g., must have an attachment from an issue) and error conditions.

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?

Only one parameter (attachment_id) with schema description coverage at 0%. Description adds 'by ID' but does not clarify the format or source of the ID. More detail would help usage.

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?

Clearly states the verb 'Downloads', the resource 'Jira attachment', and adds detail about saving to a temp file and returning the file path. Differentiates from sibling tools as the only attachment download tool.

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?

No guidance on when to use this tool versus alternatives, such as when to avoid downloading large attachments or how to obtain the attachment ID. Lack of context for usage decisions.

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