Download All Email Attachments

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON object with a download URL and specifies the endpoint, providing context beyond annotations but no unexpected behavioral traits.

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?

Description is a single paragraph of four sentences, front-loading the core purpose. Includes API endpoint details which are useful but slightly verbose. No wasted words.

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?

No output schema exists, so the description adequately explains the return value (URL to zip, JSON object). Does not mention pagination parameters (page, per_page), but the schema covers them. Tool functionality is straightforward, so completeness is good.

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?

Input schema has 100% description coverage for all 5 parameters. The description only mentions the three required ones (project_id, communication_id, email_id) without adding semantics beyond what the schema already provides. Baseline of 3 is appropriate.

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?

Clearly states the tool returns a URL to download all email attachments as a .zip file. Identifies the specific resource (email attachments) and action (download), distinguishing it from sibling tools like 'download_all_company_level_email_attachments'.

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?

Indicates when to use the tool: 'Use this to retrieve a downloadable file or export URL for Emails.' Lists required parameters but does not explicitly state when not to use it or contrast with alternatives like 'export_email_communication_to_pdf'.

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