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

Annotations already declare readOnlyHint=true, and the description adds genuinely useful context: this returns metadata only (name, size, MIME type) rather than the file body, which is an important expectation-setter. It stops short of describing auth requirements or error behavior for invalid ids.

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?

One dense sentence that front-loads the action, the returned fields, and the id provenance, followed by the REST mapping. No filler.

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 carries the return-value burden and does so by listing the metadata fields and implying no file content. For a one-parameter read tool this is nearly complete, with only error/not-found behavior unaddressed.

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% and there is a single id parameter, so the baseline is 3. The description adds real meaning beyond the schema by telling the agent where the id comes from (ticket messages), which the schema's 'Attachment id.' does not.

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) and resource (attachment metadata) and enumerates the returned fields (name, size, MIME type), which distinguishes it from enchant_get_ticket and enchant_get_customer. The REST endpoint mapping reinforces exactly what is fetched.

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?

Provides clear context for when this tool is relevant: attachment ids appear in ticket messages, so it is the follow-up call after reading a ticket. It does not name exclusions or alternatives, but no sibling tool performs attachment retrieval, so the differentiation burden is low.

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