Google Workspace MCP VE

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

No annotations are provided, so the description carries the full burden. It effectively describes the tool's behavior: it's a read operation (implied by 'Reads'), returns Markdown with preserved formatting, and details how comments are handled (default inclusion, anchor text preservation, and comment modes). However, it doesn't mention potential rate limits, authentication needs, or error conditions, leaving some behavioral aspects uncovered.

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 well-structured and concise, with two paragraphs that efficiently convey key information. The first paragraph states the purpose and differentiation from siblings, while the second explains comment handling. Every sentence adds value without redundancy, making it front-loaded and easy to parse.

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 complexity (6 parameters, no annotations, but with an output schema), the description is complete enough. It covers the tool's purpose, differentiation from siblings, and key behavioral aspects like formatting preservation and comment handling. With an output schema present, the description doesn't need to detail return values, and it adequately compensates for the lack of annotations by describing the read operation and output format.

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%, so the schema already documents all 6 parameters thoroughly. The description adds minimal parameter semantics beyond the schema: it mentions that comments are included by default and that anchor text is preserved, which relates to 'include_comments' and 'comment_mode'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, with slight credit for the added context on comments.

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 reads a Google Doc and returns it as clean Markdown, specifying it preserves formatting like headings, bold/italic, links, lists, and tables. It explicitly distinguishes from the sibling tool 'get_doc_content' by noting the difference in output format (Markdown vs plain text), making the purpose specific and differentiated.

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 provides explicit guidance on when to use this tool versus alternatives: it states 'Unlike get_doc_content which returns plain text, this tool preserves document formatting as Markdown,' directly naming the sibling tool and clarifying the key distinction. This helps the agent choose between tools based on the desired output format.

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