drive_download

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

Annotations declare a safe read (readOnlyHint=true) and open-world reach, and the description adds genuinely new behavioral context: user credentials are used, large binaries are written to a local path rather than returned inline, and text is paginated in 50k-char windows. This tells the agent exactly what to expect from the call's side effects.

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?

Front-loaded with purpose and sibling routing, then operational detail, then a compact Args/Returns block. Every sentence carries information an agent needs to call it correctly; nothing is filler.

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?

An output schema exists, yet the description still clarifies the practical shape of results (text vs. saved-file path). Together with the size limit, pagination behavior and credential note, an agent has everything needed to invoke and interpret this correctly.

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%, so the description carries the burden and does document both params: file_id as the Drive file id and offset as the character start position, explicitly noting it is ignored for binary files. It stops short of explaining offset's interaction with the 50k windowing beyond the implied pagination, but coverage is solid.

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 first sentence names a specific verb (Download) and resource (content of a non-Google-native Drive file), and the negative qualifier immediately separates it from the export flow. Combined with the explicit pointer to docs_export, an agent can distinguish it from siblings without opening a 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?

It states when to use it (uploaded files such as PDF, xlsx, txt, images), when not to (Google Docs/Sheets/Slides), and names the exact alternative (docs_export). It also gives operational bounds: 10 MB cap and text returned in 50,000-character windows with an offset for the next page.

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