docs_read

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

The word 'Read' implies a non-destructive operation, and 'full text content' indicates the return format. However, without annotations, the description does not disclose permissions, size limits, or error behavior beyond this basic indication.

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, focused sentence with no redundancy.

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 read tool with an output schema, the description provides sufficient functional clarity. It lacks usage context but is otherwise complete for basic selection and invocation.

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 does not mention the document_id parameter or its meaning. The schema provides only the parameter name and type without description, leaving the agent to infer that document_id is the Google Doc's identifier.

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 'Read the full text content of a Google Doc,' providing a specific verb (read), resource (Google Doc), and scope (full text content). This clearly distinguishes it from sibling tools that modify or search docs.

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 like drive_read_file or docs_find_replace. The description merely states what it does without contextual or exclusionary information.

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