get_issue_attachments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructionHint=false, and openWorldHint=true, so the agent knows this is a safe, repeatable read. The description adds no behavioral detail beyond the annotations – no pagination, auth, result-size, or empty-state notes. With annotations carrying the safety profile, a 3 is appropriate.

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?

Two sentences that are essentially duplicates – the second sentence ('Retrieve all attachments for an issue using its unique identifier') paraphrases the first without adding information. Front-loading is fine but the repetition wastes space.

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 single-parameter read tool with no output schema, the definition is minimally adequate. It lacks any note on return shape, nested path structure, or behavior on empty results, though annotations cover the safety profile.

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 0%, and the single parameter is a nested object (path.issueId) with only 'The issue identifier.' documented in the schema. The description does not compensate by explaining the required wrapping 'path' object or the integer format for issueId, leaving the nesting under-explained.

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?

States a specific verb (get/retrieve) and resource (attachments for an issue), clear enough to distinguish from siblings like get_test_case_attachments or get_test_result_attachments. The second sentence merely restates the first, adding no further precision.

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 when-to-use guidance, no mention of alternatives, and no exclusions. The agent must infer usage purely from the name and the issueId parameter.

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