jira_get_attachment_images

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

With no annotations provided, the description carries the full burden, and it excels: it discloses that each image is returned as an MCP image content block, that non-image attachments are ignored, that no MarkItDown extraction or MCP sampling is required, and that the structured content includes metadata and download failures. This gives the agent a clear picture of the tool's behavior and edge cases.

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 and front-loaded with the main purpose, then organized with clear Args and Returns sections. However, the Args section partially duplicates the schema's parameter descriptions, making it slightly longer than strictly necessary, though the Returns detail is non-redundant given there is no output schema.

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?

Given the lack of annotations and output schema, the description is exceptionally complete: it explains the exact return format (ToolResult with image blocks and structured content), the client compatibility requirements, the exclusion of non-image files, and provides an alternative tool. It covers all key aspects an agent needs to invoke and interpret this tool correctly.

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?

The input schema already provides 100% coverage for the three JSON parameters, so the baseline is 3. The description adds value by documenting the `ctx` FastMCP context argument, which is absent from the schema, and by clarifying defaults (e.g., max_images=10) in the Args section, though this mostly repeats schema descriptions.

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 'Fetch image attachments from a Jira issue as viewable image content,' a specific verb+resource+output combination. It explicitly contrasts with jira_summarize_attachments, which handles documents, thereby distinguishing from a sibling 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?

The description states when to use this tool: when you need image attachments as viewable content for vision-capable models. It also provides an explicit alternative: 'use jira_summarize_attachments for documents (PDF / DOCX / XLSX / CSV / …)' when non-image attachments are involved.

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