Get Drive File Download URL

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

The description discloses key behavioral traits: downloading to local disk, return type dependency on mode, expiration of HTTP URLs, and export behavior for various file types. These align with annotations (readOnlyHint, idempotentHint) and add context beyond what annotations provide, such as the 1-hour URL validity.

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 front-loaded with the core action and uses bullet points for clarity. It could be slightly more concise, but the structure effectively separates mode behavior from export format details, making it easy to scan.

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?

Given the presence of an output schema (not shown) and 100% schema coverage, the description covers the essential return behavior, export logic, and mode distinctions. It does not mention potential errors or authentication requirements, but those are likely handled elsewhere and the openWorldHint suggests external context is acceptable.

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 coverage is 100%. The description adds value by explaining the default export formats for each Google native file type and the effect of the 'export_format' parameter, which goes beyond the schema's enum list. The other two parameters are straightforward and don't need further elaboration.

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 the tool downloads a file and saves it to local disk, with specific return modes (stdio vs HTTP) and export format handling for Google native files. It differentiates from siblings like 'get_drive_file_content' by focusing on download and URL generation.

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 provides clear context on when to use the tool (downloading files) and details export format options for different file types. However, it lacks explicit guidance on when not to use it or comparisons with alternative tools like 'get_drive_file_content' for retrieving file content.

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