get_attachment

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

Annotations already mark it as a safe read operation, but the description adds rich behavioral details: how different MIME types are handled, the size limit, and the 'truncated' flag for large files. No contradiction with annotations.

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 front-load the core purpose and then efficiently detail the conditional behaviors. Every sentence contributes necessary information without redundancy.

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?

Despite lacking an output schema, the description thoroughly covers return types for various MIME categories, the truncation mechanism, and size limits. It addresses edge cases and leaves no gap in understanding what the tool returns.

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%, with each parameter described. The description adds context beyond the schema by explaining the behavior for files exceeding maxSizeBytes (truncated flag) and the default value, and clarifies that image/* types return image content. This adds meaningful nuance.

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?

Description starts with 'Download an attachment by id' – clear verb+resource. It distinguishes download from its sibling 'upload_attachment' and specifies handling per MIME type.

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?

The description explicitly states when to use the tool: to download an attachment. Although it does not list alternatives or when not to use it, the context is clear given the sibling tools and the straightforward nature of the operation.

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