read_file_content

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

Description discloses character limit (20,000) and supported file types, which adds value beyond the schema. However, since annotations are absent, full burden falls on description. It does not state whether operation is read-only, required permissions, or behavior for unsupported files.

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?

Single sentence, front-loaded with action verb, no wasted words. Every piece (action, resource, types, limit) earns its place.

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 tool with one parameter and no output schema, description covers core purpose and constraint (20,000 char limit). Missing error handling details, but overall adequate.

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 already documents file_id with description 'Google Drive file ID' (100% coverage). Description adds no additional meaning for the parameter beyond 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?

Description clearly states it reads text content of Google Drive files and lists supported types (Docs, Sheets, PDFs, plain text). This distinguishes it from sibling tools like get_file_metadata (metadata only) and upload_file (upload).

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?

Usage context is implied for reading text content, but no explicit guidance on when to use this tool versus alternatives like get_file_metadata (for metadata) or upload_file (for uploading). No when-not-to-use or exclusion criteria.

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