mail_download_attachment

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

No annotations are provided, and the description only states 'Download an attachment blob' without disclosing behavioral traits such as what happens to the file (e.g., saved locally, returned as data), permissions needed, or size limits. The output is not described, though an output schema exists.

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?

The description is concise (5 lines), front-loaded with the main action, and includes parameter descriptions in a clear args block. Every sentence adds value 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?

For a download tool with 3 parameters and an output schema (acknowledged by context signals), the description sufficiently covers what the tool does and parameter semantics. The existence of an output schema means return values need not be explained.

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%, but the description explains each parameter's purpose: blob_id as 'The blobId of the attachment (from email attachments list)', name as 'The filename to use for the download', and content_type with its default value. This adds significant meaning beyond the schema titles.

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 clearly states 'Download an attachment blob by blobId', providing a specific verb and resource. It distinguishes itself from sibling tools like mail_upload_attachment and mail_parse_email by focusing on downloading blobs.

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 implies usage context by specifying the blob_id comes from 'email attachments list', but does not explicitly state when to use this tool over others or provide exclusions. No alternatives are mentioned.

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