drive_download

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

With no annotations, the description carries the full burden and does notable work: it discloses that Google Docs/Sheets/Slides are converted by the app (e.g. to PDF), that a copy is written into the phone's Download folder, and that the file is then copied to the computer. Unstated are overwrite behavior when local_path exists, required connectivity/auth, and what happens on timeout.

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?

A single compact sentence with the resource and the two-step flow front-loaded; every clause carries information. It could be trimmed slightly but there is no padding or repetition.

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 7-parameter, fully-optional-input tool with no output schema and no annotations, the description covers the important non-obvious behavior (export format conversion, phone-side copy). It does not mention what is returned (e.g. the local file path) or how name/path/index/occurrence interact, which would have closed the remaining gap.

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 seven parameters are already documented with defaults; the description adds only the export-conversion nuance, which touches the format of what is downloaded but not any individual parameter. 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?

The description states a specific verb+resource (download a Drive file) and, unusually, the full mechanism: Drive's own Download action, then a copy to the computer. That two-stage behavior implicitly separates it from device_pull or drive_read_text, though no sibling is named explicitly.

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?

Usage is implied rather than stated — an agent can infer this is the tool for getting a Drive file onto the local machine, but there is no explicit when-to-use, no comparison to device_pull/drive_open/drive_read_text, and no note on prerequisites such as the file needing to be visible from the current Drive location.

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