drive read file text

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding genuinely new behavior: Sheets come back as first-sheet CSV, Slides get flattened to text, output is truncated at max_chars, and binary files are rejected. Truncation signaling (whether the output marks a cut-off) is not stated.

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, zero filler, with the supported formats and the cap stated up front. Every clause conveys information an agent needs.

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 two-parameter read tool with an output schema and full annotations, this is close to complete: types, conversion format, cap, and refusal of binaries are all covered. Only the file_id provenance and truncation behavior are unstated.

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 must carry the load. It does explain max_chars as a cap on output length, but not its default, units, or truncation semantics, and file_id is left entirely to inference (presumably a Drive file ID from drive_search_files). Partial compensation only.

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 names a specific verb (read) and resource (text of a file) and enumerates the supported file types, so the agent knows exactly what comes back. It does not explicitly differentiate itself from nearby siblings like docs_get_document or sheets_read_range, which is the only thing keeping this from a 5.

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?

Usage is implied (call it when you want the text content of a file), but there is no explicit when-to-use/when-not guidance and no mention of when to prefer docs_get_document, sheets_read_range, or slides_get_presentation instead. The 'binary files are refused' line hints at a boundary but is a limitation, not routing guidance.

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