Read file text

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), but the description adds real value beyond them: the 10 MB limit, the paging model, the format whitelist, and an explicit prompt-injection warning that file content is untrusted data. Only the pagination continuation behavior is left mostly implicit.

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?

Three dense sentences, front-loaded with the core action and constraints; every clause (formats, size cap, paging, untrusted content) carries information and none is wasted.

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?

With no output schema, the description still conveys the return shape through the paging hint and nextOffset reference in the schema. For a read tool whose annotations already carry safety, this is close to complete; only explicit terminal/pagination semantics for the last page are missing.

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 path, offset, and maxChars are already fully documented with defaults and bounds. The description only restates 'paged by offset/maxChars' without adding format or edge-case detail, so baseline 3 applies.

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?

Clear verb+resource (read text of a Drive file) with explicit supported formats and a size bound. It does not differentiate itself from the sibling drive_read_file, which an agent must disambiguate on its own, so it falls short of 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?

It states a key precondition ('without a sync folder') and supported file types, which implies when it applies, but there is no explicit when-to-use guidance versus drive_read_file or drive_download, and no stated exclusions for unsupported types.

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