downloadJiraIssueAttachment

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description usefully adds that the URL is 'short-lived' and that output includes a local save command, but it omits any indication that savePath writes a file to the local filesystem — a side effect worth flagging against readOnlyHint.

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 front-loaded sentence with no filler; the primary result (the URL) leads and the secondary return artifact follows.

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?

With no output schema, the description does carry the burden of describing returns and does so partially (URL plus command). However it leaves the savePath file-write behavior and the undocumented attachmentId unexplained, which is a meaningful gap for a two-parameter tool.

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 only 50%: savePath is described in-schema but attachmentId has no description anywhere. The description only loosely gestures at savePath behavior ('a local command to save the file') and says nothing about what attachmentId expects, an identifier format, or where to obtain it.

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 gives a specific verb ('Get a download URL') and resource ('an attachment'), and its output-shape detail (a short-lived URL plus a local save command) separates it from the sibling uploadAttachmentToJiraIssue. It never names a sibling explicitly and omits the savePath write-to-disk behavior, so it stops short of a 5.

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?

There is no when-to-use/when-not guidance and no mention of alternatives among the many Jira siblings. It also doesn't tell the agent when to prefer the URL-only path versus supplying savePath, so the caller must infer the two usage modes.

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