drive_files_download

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: return formats (text content, base64-encoded string, exports for Google-native files) and default behaviors (plain text for Docs, CSV for Sheets). However, it omits critical details like authentication needs, rate limits, error conditions, or whether the operation is read-only/destructive.

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 efficiently structured in three sentences, each adding distinct value: purpose, return formats, and Google-native file handling. There is no wasted text, and key information is front-loaded.

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 complexity (download operation with format handling), no annotations, and no output schema, the description is moderately complete. It covers core functionality and return formats but lacks details on authentication, errors, rate limits, or response structure, which are important for a tool with multiple parameter-dependent behaviors.

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%, providing a strong baseline. The description adds minimal value beyond the schema: it clarifies that exportMimeType applies to 'Google-native files' and savePath is for 'binary files', but doesn't explain parameter interactions or provide examples beyond what's in the schema descriptions.

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 specific action ('Download a file's content from Google Drive') and resource ('file'), distinguishing it from siblings like drive_files_get (metadata) or drive_files_export (specific export tool). It explicitly mentions what is downloaded (content vs. 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 provides clear context on when to use this tool for downloading content, with implicit differentiation from siblings like drive_files_get (metadata retrieval) and drive_files_export (focused export). However, it lacks explicit 'when-not' guidance or named alternatives for overlapping use cases.

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