read_doc

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

With no annotations provided, the description carries the burden of disclosing behavior. It communicates a read-only operation and specifies the returned fields (id, title, text content), but it leaves out permission requirements, error cases, and text format details.

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 compact, front-loaded, and uses a clear Args/Returns structure without unnecessary fluff. The Returns section is somewhat redundant with the existing output schema, but it still adds useful clarity at minimal length.

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?

The tool has only one required parameter, no nested objects, and a documented output schema, so the description is largely sufficient for correct invocation. It lacks explicit error or permission notes, but for a simple read operation these are not critical gaps.

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%, so the description must compensate for the bare string parameter. 'document_id: ID of the document' adds minimal meaning beyond the parameter name, but does not provide format guidance, examples, or how to locate the ID.

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 a specific verb ('Read') and resource ('Google Doc'), making the tool's function immediately clear. It also distinguishes itself from siblings like create_doc, update_doc, and export_pdf, which involve different operations.

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 clearly implies the tool is for retrieving Google Doc content, which gives some usage context. However, it does not explicitly contrast with alternatives such as download_file or export_pdf, nor does it state when not to use this tool.

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