Merge Cells

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

Annotations provide no safety hints (no readOnlyHint or destructiveHint), so the description carries the full burden of behavioral disclosure. It states the core action but omits critical side effects: merging typically keeps only the upper-left cell value, discarding other values, and may fail on overlapping merges. This is a notable gap for a mutating operation.

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 concise and well-structured: a one-sentence purpose followed by a clear Args/Returns block. Every line adds value with no redundancy.

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 description covers the core operation and parameters, but lacks important context for safe invocation: no mention of data loss on merge, restrictions on valid ranges, or error conditions. The return value is only described as 'JSON confirmation', which is vague. Given the absence of an output schema, more behavioral detail would be needed for full completeness.

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 property descriptions are absent (0% schema coverage), but the description fully documents all three parameters with meaning: workbook name/path, sheet name, and A1-style range address, including defaults. This compensates completely for the schema gap.

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 ('Merge'), a resource ('a range'), and the outcome ('into a single cell'). This clearly differentiates it from siblings like unmerge_cells and get_merge_info.

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 does not mention unmerge_cells for undo, get_merge_info for inspecting merges, or any exclusions. The usage context is only implied by the tool name.

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