drive_file_download

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

No annotations are provided, so the description carries the full burden. It only discloses the export MIME type behavior for certain file types but omits other important behavioral traits like overwrite behavior, authentication requirements, rate limits, or what happens when saving to a path. The disclosure is minimal.

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 sentences with no waste. The first sentence states the core purpose, and the second adds essential nuance. Structurally efficient, though could be slightly more organized with parameter hints.

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?

The tool has 4 parameters, no output schema, and no annotations. The description is incomplete: it does not explain all parameters, constraints (e.g., file size limits), or what the tool returns (e.g., whether it writes to a file or returns binary). The export note is helpful but insufficient.

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 0%, meaning parameters are not described in the schema. The description adds meaning for `export_mime_type` with examples, but does not explain `account`, `file_id`, or `save_to`. With 4 parameters and zero schema descriptions, the description should compensate more fully.

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 'Download a file' with a specific verb and resource. It adds crucial detail about exporting Google Docs/Sheets/Slides with `export_mime_type`, distinguishing it from sibling tools like `drive_file_get` which might only retrieve metadata.

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 implies usage for downloading files and hints at when to use `export_mime_type`, but it does not explicitly state when to use this tool versus others (e.g., `drive_file_get` for metadata) or provide exclusions. Usage context is clear but not comprehensive.

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