drive_get_full_file_content

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It warns that the response 'can be very large and may overload your context window', which is a critical behavioral trait that annotations would not capture. This is a significant, honest disclosure of a potential risk.

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?

The description is a single, front-loaded sentence that immediately warns about the size issue, then gives a usage condition and alternatives. Every clause earns its place; there is no redundancy or filler.

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 simple but potentially hazardous read operation, the description covers the key context: the full-content nature, the risk of large responses, and the existence of safer alternatives. Since there is no output schema, the description adequately explains the return value as the entire file content. This is complete for an agent to make an informed decision.

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 description adds no additional meaning to the parameters beyond the schema, which already provides 100% coverage with descriptions for both accountId and fileId. The baseline of 3 applies because the schema does the heavy lifting, and the description doesn't need to compensate.

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 explicitly states 'Returns the ENTIRE file content' with a specific verb and resource, and it distinguishes itself from the sibling tools drive_get_file_content (preview) and drive_download_file. This clearly conveys what the tool does and how it differs from alternatives.

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 usage guidance: 'Only use this when you genuinely need the complete file (e.g., for analysis or transformation)' and names the alternatives to prefer for browsing or saving large files. This tells the agent exactly when to select this tool and when not to.

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