drive.read_file

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

Annotations are absent, and the description only states 'read', which implies a non-destructive operation but does not mention auth requirements, rate limits, or limitations (e.g., binary files vs text). No additional behavioral context provided beyond the basic action.

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?

One sentence, front-loaded with verb 'read', no waste. It efficiently conveys the core purpose without irrelevant details.

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 simple read tool, the description provides core purpose, but lacks details about supported file types, output structure, or relationship to sibling tools. Output schema exists but is not referenced. Given no annotations and minimal schema, more context is needed for reliable invocation.

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 has two required parameters (account, file_id) with no descriptions. Description does not explain what account refers to or how to obtain file_id. With 0% schema description coverage, the description fails to compensate for the lack of parameter details.

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?

Description states 'Read metadata and text content of a Drive file.' This clearly identifies the tool's purpose as reading a specific Drive file, distinguishing it from sibling drive.list_files which lists files. Verb 'read' is specific and the resource is explicit.

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?

No mention of when to use this tool versus alternatives. Does not indicate that drive.list_files should be used to obtain file_id, or that this is for reading content after listing. No explicit guidance on usage context or prerequisites.

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