download_documents_bulk

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds that the response is a base64-encoded ZIP file, which is useful behavioral context. However, it doesn't disclose details like file size limits, timeout behavior, or how the ZIP is structured (e.g., folder hierarchy), which could matter for large bulk downloads.

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?

Two short sentences with no filler. The core action and return format are front-loaded. It could arguably include a hint about the 'content' parameter's effect on ZIP contents, but the schema covers that.

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 bulk download tool with readOnlyHint=true and full schema coverage, the description is mostly adequate. The main gap is that it doesn't mention the relationship to download_document (single vs. bulk) or any practical caveats like response size, which an agent might need to know when choosing between the two tools.

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 100%, so the schema already documents all four parameters. The description adds no parameter-specific meaning beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('Download') and resource ('multiple documents as a ZIP archive'), which clearly distinguishes it from single-document download tools like download_document. It doesn't explicitly name a sibling alternative, but the bulk vs. single distinction is clear enough from the name and description.

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 for downloading multiple documents at once, and the sibling list includes download_document for single downloads, providing implicit context. However, it doesn't explicitly state when to prefer this over download_document or mention any limits or prerequisites beyond the schema's maxItems.

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