drive_download_file

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

The description discloses the return format as a JSON string with the saved path and byte size, and mentions the error case when export_mime_type is missing. This adds meaningful behavior beyond the annotations' readOnly/idempotent hints, though it doesn't cover details like overwrite behavior or auth requirements.

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 compact and front-loaded, with the core action in the first sentence and return behavior in a short second section. Every sentence earns its place; there is no redundant or filler text.

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?

Together with the detailed input schema, the description provides enough context to call the tool correctly, including the export requirement and return shape. Minor gaps like overwrite behavior and permission requirements exist, but they are not critical for selecting or invoking this tool.

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?

Although the schema already documents file_id, destination_path, and export_mime_type, the description adds important semantics around export_mime_type: it is required for Google-native files and its absence produces an error. This enriches the parameter's meaning beyond the raw schema text.

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 clearly states a specific action—'Download a Drive file to a local path'—and adds the export behavior for Google-native files. This distinguishes it from sibling tools like drive_read_file_content or drive_get_file_metadata, which serve different purposes.

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 a clear usage context: use when downloading a Drive file to a local path, and when exporting native files. However, it does not explicitly state when not to use it or mention alternatives such as drive_read_file_content for reading file content without downloading.

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