drive_files_download

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and scope. The description adds valuable context about return types (text vs base64) and export behavior for Google-native files, going beyond the annotations without contradicting them.

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 clear front-loading of the main purpose. However, 'plain text by default' is somewhat redundant with the schema's stated default, and the sentence about Google exports could be tightened without losing meaning.

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 description covers the main return scenarios (text, binary, Google-native exports) and works with the annotations to form a fairly complete picture. However, it does not address the overlap with drive_files_export, leaving an agent uncertain about which tool to use in that case. No output schema exists, so description bears the burden of explaining return values, which it does for the core cases.

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 each parameter is already documented. The description's mention of 'plain text by default' and binary/base64 behavior adds only marginal context that mostly echoes the parameter descriptions. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a clear verb+resource ('Download a file's content from Google Drive') and specifies return behavior for text, binary, and Google-native files. It differentiates from list/get tools but does not explicitly distinguish itself from the sibling drive_files_export, which also handles exporting Google-native formats.

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 no when-to-use or when-not-to-use guidance. It mentions exporting Google Docs/Sheets/Slides, which overlaps with the sibling drive_files_export, but does not explain when to choose one over the other. No alternatives or exclusions are named.

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