download_attachments

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

No annotations are provided, so the description carries full burden. It states the action but fails to disclose side effects (e.g., file overwrites), error behavior, or resource implications. The existence of an output schema is not mentioned, leaving agents uninformed about return values.

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 minimal and front-loaded, with one clear sentence followed by a concise args list. No redundant information is present.

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 only 2 parameters and an output schema, the description covers parameter meanings but omits any mention of output, error scenarios, or prerequisites like authentication. It is adequate but not thorough for a download tool.

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?

Despite 0% schema description coverage, the description adds meaningful semantics: item_id is 'The Exchange ItemId of the email' and target_folder is 'Local directory to save files (default /tmp/attachments)'. This compensates for the schema gap.

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 clearly states 'Download all file attachments from an email to disk,' specifying the verb, resource (attachments from an email), and destination. It distinguishes itself from sibling 'download_event_attachments' by targeting 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?

The description implies usage (downloading email attachments) but lacks explicit guidance on when to use vs. alternatives like 'download_event_attachments' or prerequisites (e.g., having the item_id, needing to log in). No exclusions are given.

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