get_attachment

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

The readOnlyHint annotation already covers the safety profile, and the description is consistent with it. The phrase 'optionally rendering its image inline' adds a small behavioral detail tied to include_image, but the description does not clarify what the fetched attachment actually returns or what happens when inline rendering is false.

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 short sentence with no filler, and the core operation is front-loaded before the optional rendering behavior. Every word earns its place.

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 must explain what the returned attachment actually is—binary content, metadata object, URL, or rendered inline image—but it leaves this ambiguous. It also omits prerequisites and error behavior, making it incomplete for an agent to invoke confidently.

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%, so the description needed to carry more weight. It gives some meaning to include_image via 'rendering its image inline,' but attachment_gid receives no elaboration beyond the obvious 'which attachment,' and no value formats or constraints are provided.

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 names a specific verb and resource ('Fetch one attachment') and adds a distinct behavioral caveat about optional inline image rendering. This clearly separates it from sibling tools that target projects, tasks, or comments.

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?

There is no guidance about when to choose get_attachment over the sibling tools or what prerequisites apply, such as first obtaining the attachment_gid from a task. The only implied context is the resource name, which is not enough routing guidance.

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