download_attachment

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

No annotations are present, so the description carries the full burden, yet it discloses only the basic download action. It omits side effects such as file overwrite behavior, whether save_path must already exist, and what happens when the attachment or message is missing. For a tool that writes to the filesystem, this is a significant gap.

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?

A single eight-word sentence with the verb front-loaded and zero filler. Every word earns its place, and nothing is redundant with the schema or parameters.

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?

The output schema presumably covers return values and the schema documents all parameters, but the description omits usage context and safety caveats for a disk-writing operation: collision handling, path creation behavior, and relation to sibling email tools. For a non-annotated tool, this is only minimally viable.

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% — every parameter has a description, including defaults for filename and save_path. The phrase 'specified location' loosely maps to save_path but adds no syntax, path-format, or behavior detail beyond what the schema already documents, so the 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?

The description states a specific verb (download) plus the resource (email attachment) and the target behavior (to a specified location). No sibling tool retrieves attachment binaries — send_email composes and read_email reads messages — so an agent can distinguish it without opening the schema.

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 gives no when-to-use guidance, prerequisites, or exclusions. It never connects to related flows like read_email or send_email, leaving the agent to infer the tool's role solely from its name.

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