drive_download_file

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

With no annotations, the description carries the full burden, and it does disclose real behavior: native Workspace files are auto-exported with stated default formats, and export_mime_type overrides that. It is silent on authentication requirements, overwrite behavior when dest_path already exists, and rate/size limits on 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 tight sentences with the core action and destination front-loaded, followed immediately by the one non-obvious behavior (native file export). Nothing is wasted.

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?

There is no output schema, so the description should ideally say what the call returns (e.g., the written path) and whether an existing file is overwritten. It covers the download and export semantics adequately but leaves these operational details unspecified.

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 baseline is 3. The description adds genuine meaning for export_mime_type by explaining the default export mapping that applies when it is omitted, but adds nothing for email, dest_path, or file_id_or_url beyond the schema.

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 pairs a specific verb (download) with a specific resource (Drive file) and a destination constraint ('to an exact local path'), which separates it from read-style siblings like drive_read_file and drive_get_file. It stops short of naming any sibling explicitly, so the differentiation is inferable rather than stated.

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 by the export rule: use export_mime_type only when you need a non-default format for a native Workspace file. There is no explicit when-to-use/when-not guidance and no mention of when to prefer drive_read_file over downloading.

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