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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: 50 MB / 10 MB export limits, 20,000-character chunks, totalChars/truncated/nextOffset response fields, and the not-connected response shape with a connect link. It does not discuss auth failures beyond the no-Drive case or any rate limits, so it stops short of full disclosure.

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?

Four dense sentences, each carrying distinct information: capability and limits, file_id source, pagination contract, and the no-connection fallback. Zero filler, and the core purpose is front-loaded in the first clause.

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 carries the burden of describing return values, and it does so precisely (text chunks, totalChars, truncated, nextOffset, connected false plus link). For a read-only single-file tool with a fully documented 4-parameter schema, nothing an agent needs is 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 coverage is 100%, so both file_id provenance and offset/person/project semantics are already documented. The description adds marginal meaning by fixing the chunk size at 20,000 characters, which clarifies what an offset unit actually is, but it says nothing about the person or project parameters and otherwise restates the schema.

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?

States a specific verb and resource ("Read the text of one connected Google Drive file") and enumerates exactly which file types are supported and their size ceilings. An agent can distinguish it from siblings like storage_write_google_drive_file or storage_get_file without opening any 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?

Routes the agent to search_google_drive as the source of file_id and explains the pagination loop (while truncated is true, nextOffset is the next offset). It does not explicitly exclude sibling tools such as storage_get_file or storage_list_files, so an agent must infer that this is the text-extraction path, but the usage context is otherwise clear.

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