List Tracker issue attachments

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond them: it returns metadata only (ItemList[Attachment]) and cannot deliver binary content, steering the agent away from an impossible download attempt.

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?

Front-loaded with the resource and returned fields, followed by the download limitation. Three tight sentences; the CLI note is slightly verbose but earns its place by preventing a futile download call.

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 compensates by describing the return shape and fields, and it discloses the download limitation. Complete enough for a single-parameter read tool, though it omits pagination behavior.

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 100% and issue_key is documented in the schema (e.g. 'JUNE-2'). The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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+resource ('Files attached to a Tracker issue') and enumerates the returned fields (name, size, MIME type, uploader, download URLs), so the agent knows exactly what it lists. It does not explicitly distinguish itself from the sibling tracker_attachments_get (single attachment) or tracker_entities_attachments_list, so it falls just short of full sibling differentiation.

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?

Gives clear usage context ('use it to discover a file's id and name') and an explicit when-not-to: raw byte download is CLI/SDK-only, not an MCP payload, with the exact CLI command. It stops short of naming MCP alternatives for fetching a single attachment's metadata.

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