Download multiple files

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. The description's "Read operation" merely echoes readOnlyHint and adds nothing new — no note on credential scope for the private account, no rate/limit behavior, no mention that results are written out of model context.

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 fragments with no wasted words, but the problem here is under-specification rather than conciseness. Brevity at this level of complexity leaves the agent without the routing and prerequisite information it needs.

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 9-parameter tool with a nested payload object, a required output_file with non-overwrite/private-directory semantics, and mutually exclusive payload_file vs payload vs body flags, the description covers none of the call-shaping rules. With no output schema the burden falls entirely on the description, and it does not carry it.

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 all nine parameters (including the nested payload object and the required output_file) are already documented in the schema. The description adds no syntax, format, or mutual-exclusivity detail, so the baseline 3 applies.

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?

"Download multiple files" states a verb and resource and hints at scope (plural vs the singular sibling download_file), but it is essentially the title restated with a two-word addendum. It gives no indication of what files are being downloaded, from where, or under what identity.

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?

There is no when-to-use guidance at all. The agent gets no cue for choosing this over download_file, download_artifact_file, download_skill_file, or the upload_* siblings, and no prerequisites (run_id/user_id/project_id either-or) are mentioned.

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