merge_cells

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

Annotations provide destructiveHint: true, indicating mutation, but description adds no further behavioral context (e.g., what happens to cell contents, only top-left value preserved). Meets minimal transparency.

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?

Single sentence, no wasted words, but lacks crucial detail for a destructive operation. Appropriately concise but under-informative.

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 destructiveHint annotation and existence of sibling tools, description should explain return value, irreversible impact, and prerequisite cells. It fails to provide a complete picture.

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 coverage is 0%, so description should compensate. While parameter names are self-explanatory, no details like valid cell reference formats (e.g., 'A1') or that start_cell and end_cell define the range are provided.

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 'Merge a range of cells' clearly states the action and resource, but does not differentiate from sibling tools like unmerge_cells or mention constraints such as requiring a valid existing sheet.

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?

No guidance on when to use this tool versus alternatives (e.g., unmerge_cells) or prerequisites. No mention of required cell format or that merging overwrites data.

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