docs_read

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

No annotations are provided, so the description is the sole source of behavioral disclosure. It clearly states that the tool reads the full text content, which is a safe, read-only behavior. However, it does not describe nuances like formatting preservation, size limits, or authentication requirements, which would be useful context for an agent.

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, clear sentence that directly states the tool's function. There is no redundant or extraneous content, and the key 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?

Given the tool's simplicity (one parameter) and the presence of an output schema, the description covers the essential purpose without needing to explain return values. However, the lack of annotations and usage guidance leaves minor context gaps, particularly around when to select this tool over similar read tools.

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 schema has a single parameter `document_id` with no description, and the tool description offers no additional details about it. Since schema coverage is 0%, the description fails to compensate, leaving the agent to rely on the parameter name alone. The description adds no value beyond the raw 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?

The description clearly states the action ('Read') and the resource ('Google Doc'), and specifies 'full text content' which defines the scope. However, it does not explicitly distinguish from sibling tools like `drive_read_file`, so it lacks a clear differentiation.

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 implies usage for reading a Google Doc but provides no explicit guidance on when to use this tool versus alternatives such as `drive_read_file` or `docs_*` tools. No exclusions or alternative scenarios are mentioned, leaving the agent to infer the context.

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