Download Attachments

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

Description adds value beyond annotations by explaining that attachments are returned as base64-encoded embedded resources for MCP protocol compatibility, avoiding filesystem access. This is useful behavioral context. Annotations already confirm read-only, so no contradiction.

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?

Description is concise but includes a docstring-style breakdown of Args and Returns. It's front-loaded with purpose and adds necessary detail about return format. Could be slightly tighter, but it's well-structured.

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 simple read-only tool with one parameter and no output schema, the description covers purpose, parameter, and return format. It lacks error handling info (e.g., what if issue has no attachments or key invalid), but overall it's fairly 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 coverage is 100% with a clear description for issue_key. The description's Args section repeats the same info ('Jira issue key') without adding new meaning, so it meets the baseline 3.

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?

Description clearly states 'Download attachments from a Jira issue.' It specifies the action (download), resource (attachments), and source (Jira issue), making it distinct from sibling tools like jira_get_issue or jira_search that do not download attachments.

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 vs alternatives (e.g., jira_get_issue which returns issue data without attachments). No explicit when-not-to-use or exclusion criteria, leaving the agent to infer context from the name alone.

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