Bulk download documents

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

Annotations already indicate a safe, read-only, idempotent operation. The description adds useful behavior beyond that: the archive is written to a download directory and the response is the archive path, not file contents. This gives the agent a clear model of what happens when invoked.

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 two sentences, tightly scoped, and front-loads the core action and key behavioral detail. Every sentence earns its place with no redundant filler.

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 moderate-complexity tool with five parameters and no output schema, the description covers the key behavioral contract: archive creation, destination, and return type. It does not detail all parameter interactions, but those are sufficiently documented in the schema, and annotations cover safety and idempotency.

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 60%, with descriptions for content, filename, and follow_formatting; documents and compression rely on their names/enum values. The description itself adds no parameter-level detail, but the schema carries most of the needed meaning for those parameters.

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: downloading several documents as one zip archive, written to the download directory. It also clarifies the return value is the archive path, not contents. This clearly distinguishes it from siblings like download_document or bulk_edit_documents.

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 clear context for when to use the tool: when downloading several documents as a single archive. It does not explicitly mention alternatives or exclusions, such as using download_document for a single file, but the bulk scope is clear from both title and description.

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