Google Workspace MCP VE

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that Google Docs auto-converts the email into a rich person chip, which is useful, but fails to address critical aspects like required permissions, whether this is a mutation (likely yes), error conditions, or rate limits. The description is insufficient for a mutation tool with no annotation coverage.

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 front-loaded with the core purpose in the first sentence, followed by a clarifying detail. Both sentences earn their place by providing essential information without redundancy, making it appropriately sized and efficient.

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 (mutation with 5 parameters), no annotations, and an output schema (which reduces the need to describe return values), the description is moderately complete. It covers the basic operation and auto-conversion behavior but lacks details on permissions, errors, or usage context, leaving gaps for an agent to invoke it correctly.

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 description coverage is 80%, so the baseline is 3. The description adds minimal value beyond the schema, mentioning that the 'person's email is inserted as text with a `mailto:` link,' which slightly clarifies the 'email' parameter but doesn't compensate for the 20% coverage gap or provide additional context for parameters like 'index' or 'tab_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 clearly states the specific action ('Insert an @mention person chip') and resource ('at a specified index'), distinguishing it from sibling tools like insert_doc_elements or insert_doc_link. It precisely defines the tool's function without being tautological.

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 no guidance on when to use this tool versus alternatives like insert_doc_elements or insert_doc_link, nor does it mention any prerequisites or exclusions. It lacks context for tool selection among siblings.

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