download_file

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

No annotations exist, so the description carries the full burden and does well: it discloses Google-native export behavior with per-type defaults, the format override, and the explicit refusal to overwrite unless overwrite=true — a key destructive-safety trait. It omits authentication requirements, error/partial-write behavior, and whether it creates parent directories.

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?

Three tight sentences, front-loaded with the core action, then the two behavioral caveats that matter most. No filler or repetition of the tool name.

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 download tool with no output schema and no annotations, the description covers the essential behaviors (export mapping, overwrite protection). Missing are the return value or returned path and any auth/permission context, but nothing critical to invoking it correctly is absent.

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?

With 50% schema description coverage, the description compensates: it explains format's default-per-file-type behavior and clarifies overwrite's polarity ('refuses to overwrite unless true'), which the bare boolean property does not. destinationPath's file-or-directory duality is left to the schema, and fileId is never described, but the added meaning exceeds the baseline.

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?

States a specific verb and resource with clear directionality ('Save a file to a local absolute path'), which inherently separates it from upload_file (local→Drive) and read_file_content. An agent can identify the tool's job without opening the schema.

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: nothing says when to prefer this over read_file_content or upload_file, and no prerequisites (auth scopes, target directory existence) are given. The export-format and overwrite notes are operational detail, not when-to-use guidance.

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