docs_read_text

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

Because no annotations are provided, the description carries the full behavioral burden. It usefully discloses the return shape, that paragraphs are joined with newlines, and that formatting is not represented. It does not explicitly state that the operation does not modify the document, but 'read' and the read-before-replace guidance make that non-mutating behavior strongly clear.

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 three tightly packed sentences: purpose, parameter clarification, then return and usage context. Every sentence earns its place and there is no redundant or filler content.

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 one-parameter read tool, the description covers input format, return contents, text formatting behavior, and the recommended call order relative to docs_replace_body. With an output schema also present, no essential information is missing.

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 description coverage is 0%, but the description fully compensates for the single parameter: document_id is the token in the Google Docs URL, with an exact URL template. This adds the practical meaning that a bare string schema cannot convey.

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 first sentence states a specific verb and resource: 'Read a Google Doc's text content via the Docs API.' It further clarifies the output fields and implicitly separates this read operation from the docs_append_text and docs_replace_body siblings by positioning it as the read step.

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 an explicit workflow instruction: 'Read before docs_replace_body so the rewrite starts from what is actually there.' This tells the agent exactly when to call the tool and why, referencing a concrete sibling for the write step.

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