download

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the key side effect (writes to a local cache) and the return semantics (local paths, not bytes), but it omits details such as caching behavior, auth requirements, force-refresh, 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?

Two short sentences, with the action front-loaded. Every clause earns its place: destination, side effect, and output format are each addressed without waste.

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?

Given a one-parameter schema and an output schema, the description is mostly complete: it names the action, destination, and return semantics. The main gap is parameter format/examples, but the tool is simple enough that the description covers the essential context.

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 coverage is 0%, so the description must compensate. It does not clarify what the 'paths' parameter accepts – Drive paths, filenames, globs, or IDs – besides the generic implication from 'Download Drive files.' An agent cannot reliably construct correct arguments from this.

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 Drive files' – and adds a concrete destination ('to the local cache directory'). It also distinguishes output behavior from siblings by adding 'Returns local paths, not bytes.'

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 guidance about when to use this tool versus alternatives like read_text, search, or list_folder. The verb 'Download' implies the use case, but no explicit when/when-not or alternative exclusions are given.

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