drive_read

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

With no annotations provided, the description carries the full burden. It reveals export behavior for Google Docs/Sheets/Slides, which is important. However, it does not mention what happens for other file types, authentication requirements, or that the operation is read-only (which would be expected but 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 front-load the purpose and key behavior. No redundant or extra information. Every sentence contributes value.

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?

The description is adequate for a simple read tool but lacks details on the return format for non-exported files (e.g., binary files) and does not mention any limitations or error conditions. For a tool with no output schema, more detail on what the response contains would be beneficial.

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?

The sole parameter fileId is described in the schema ('The ID of the file to read'), and the tool description adds no additional meaning or context beyond that. The description does not explain how to obtain the fileId or any constraints (e.g., format, required length).

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 clearly states the tool reads file content from Google Drive and specifies export behavior for Google Docs/Sheets/Slides ('Exports Google Docs/Sheets/Slides as text/csv'). This distinguishes it from sibling tools like drive_download_file or drive_export_file.

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 guidance is given on when to use this tool versus alternatives such as drive_download_file (for binary download) or drive_export_file (for export in specific formats). The description implies usage for text/csv exports but does not clarify when to choose this over other read-like tools.

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