download_attachments

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses batch size, input-order preservation, and deduplication of unique files, but says nothing about permissions, rate limits, download destination, return behavior, or error handling.

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 a single compact sentence with no wasted wording and front-loads the core action. However, the phrase 'unique files' is cryptic without further context.

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 batch-download tool with an opaque array-of-objects parameter and no output schema, the description is too thin. It leaves the agent unable to determine what to put in items or what the operation 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?

The sole parameter, items, has 0% schema description coverage and is not explained in the description. Phrases like 'input order' and 'unique files' hint that items is an ordered list of file references, but the required object structure and accepted identifiers remain undefined.

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 and resource: download attachments, and adds batch-size scope. It is clear but does not distinguish this batch tool from the sibling download_attachment (singular) or list_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?

It gives no guidance on when to use this tool versus download_attachment, list_attachments, or other attachment-related siblings. It also omits prerequisites, such as whether attachments must first be identified via list_attachments.

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