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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds genuine value by enumerating the returned fields and signalling that content is retrieved via a URL rather than returned inline, but it says nothing about auth/account scoping (handled only in the schema) or behavior on a missing or inaccessible ID.

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 short sentences, zero filler, with the operation and its return payload front-loaded. Nothing in the text is redundant with the name or could be dropped without losing information.

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 two-parameter read-only lookup with full schema coverage, the description covers the essentials, and the enumerated return fields compensate for the absent output schema. The only shortfall is that it does not explain how the returned content URL should be used to actually retrieve the file.

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%, with both the account and attachment_id parameters documented in the schema itself, so the baseline of 3 applies. The description adds no meaning beyond 'by its ID', such as where attachment IDs come from or whether the account parameter changes visibility.

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 states a specific verb and resource ('Get metadata for a Jira attachment by its ID') and immediately names the returned fields, so an agent knows this is a metadata lookup rather than a download. It is distinguishable from jira_add_attachment by the verb and from confluence_get_attachment by the Jira resource, though it never explicitly contrasts with those siblings.

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?

Usage is only implied: 'by its ID' tells the agent a valid attachment ID is a prerequisite, and 'content URL' hints the actual bytes require a separate fetch. There is no explicit statement of when to prefer this over downloading the attachment, nor any exclusions or alternative tools named.

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