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

With no annotations, the description must carry behavioral disclosure, and it does: it explains type-dependent return formats (Docs/Slides as text, data/code files as themselves, images as viewable pictures), and notes refusals for spreadsheets and PDFs. It does not discuss permissions or auth, but for a read operation this is a strong 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?

Three sentences deliver the purpose, supported formats, exclusions, routing to a sibling tool, and id source with no filler. The most important information is front-loaded.

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 no output schema, the description covers return behavior, exclusions, and how to obtain the required id. Nothing essential for an agent to correctly select and invoke the tool 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 description coverage is 50%: mailbox is fully described in the schema, but itemId has no description. The description compensates somewhat by telling the agent to get the id from list_gdrive_items or search_gdrive_items, but it does not directly define itemId as the file identifier or describe expected format.

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 states a specific action ('Open one file and return what is in it') on a clear resource (Drive files), and the title reinforces it. It differentiates itself from sibling read_google_sheet_range by explicitly refusing spreadsheets, and from read_onedrive_file by being Drive-specific.

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?

The description gives explicit when-to-use guidance: use this for supported file types, avoid spreadsheets in favour of read_google_sheet_range, and avoid PDFs since they are unsupported. It also instructs the agent where to obtain the required id, from list_gdrive_items or search_gdrive_items.

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