docs_get

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

The description adds 'content and metadata' to the behavior, which is consistent with the readOnlyHint annotation. However, it does not disclose additional behavioral traits such as the format of returned content, rate limits, or required permissions. The annotation already indicates read-only, so the description provides marginal extra value.

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 concise sentence that is front-loaded with the core purpose. Every word earns its place; there is no redundancy or unnecessary detail.

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 simple input (one parameter with full schema coverage) and annotations covering the read-only behavior, the description is adequate but not rich. It does not mention the output structure, which could be helpful for an agent. No output schema exists to compensate, so slightly more detail could 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 schema covers 100% of parameters with a description for documentId. The tool description does not add additional semantic meaning beyond what the schema provides, so baseline score is appropriate. No parameter details are missing.

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 retrieves a Google Doc's content and metadata, using a specific verb ('Get') and resource ('Google Doc'). It differentiates from sibling tools like docs_batchUpdate (which modifies) and sheets_get (different resource type), though it doesn't explicitly highlight these distinctions.

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 provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., document must exist), when not to use it, or scenarios where other tools like docs_batchUpdate or drive_files_get would be more appropriate.

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