Google Docs MCP Server

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

No annotations are provided, so the description carries full burden. It mentions the TOC is 'auto-generated' and 'updates automatically,' which are useful behavioral traits. However, it lacks critical details: whether this is a mutation requiring write permissions, if it overwrites existing content at the index, what happens on errors, or rate limits. For a mutation tool with zero annotation coverage, this is insufficient.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by two sentences adding essential context. Every sentence earns its place by clarifying functionality without redundancy, making it efficient and well-structured.

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 moderate complexity (2 parameters, mutation operation), no annotations, but with an output schema (implied by context signals), the description is reasonably complete. It explains what the tool does and key behaviors, though it could benefit from more detail on permissions or error handling. The output schema likely covers return values, reducing the need for that in the description.

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 100%, with clear descriptions for 'document_id' and 'index' in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. According to rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description.

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 specific action ('insert a table of contents') and resource ('at the specified index'), with additional detail about what the table of contents contains ('auto-generated from document headings HEADING_1 through HEADING_6'). It distinguishes from sibling tools like 'insert_text' or 'insert_image_from_url' by specifying this unique document formatting function.

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 context through 'auto-generated from document headings' and 'updates automatically when headings change,' suggesting it should be used when headings exist and dynamic updates are needed. However, it doesn't explicitly state when to use this tool versus alternatives (e.g., manual TOC creation or other insertion tools) or provide exclusions, leaving some ambiguity.

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