Google Docs MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the operation ('unmerge', 'splits back') but doesn't disclose critical traits like whether this is a destructive mutation, what permissions are required, how errors are handled (e.g., if the cell isn't merged), or the effect on table structure. The description is technically accurate but lacks operational context.

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 extremely concise with two sentences that directly state the action and effect. Every word earns its place, and it's front-loaded with the primary purpose. There's no redundancy or unnecessary elaboration.

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 (a mutation on table cells), no annotations, and the presence of an output schema (which handles return values), the description is minimally adequate. It states what the tool does but lacks context about prerequisites, side effects, or error conditions. The output schema relieves the description from explaining returns, but more behavioral disclosure would be beneficial.

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 4 parameters with clear descriptions. The description adds no parameter-specific semantics beyond implying that parameters identify a merged cell. This meets the baseline of 3 when schema coverage is high, but doesn't provide extra value like explaining coordinate relationships or edge cases.

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 action ('unmerge', 'splits back') and resource ('table cells'), making the purpose immediately understandable. It distinguishes from siblings like 'merge_table_cells' by specifying the reverse operation. However, it doesn't explicitly differentiate from other table manipulation tools like 'delete_table_column' or 'update_table_cell_style' beyond the core action.

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. It doesn't mention prerequisites (e.g., requires a merged cell to exist), nor does it reference sibling tools like 'merge_table_cells' for context. Usage is implied from the action but not explicitly stated.

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