merge_cells

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

No annotations are provided, so the description should fully disclose behavioral traits. It fails to mention side effects (e.g., cell content handling), constraints (e.g., adjacent cells only), or return values for this mutation 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 with two sentences, and the parameters are listed in a structured args block. The note about session_id is efficient, but the overall structure could be more front-loaded.

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 no annotations, schema descriptions, and a true output schema (not provided), the description misses crucial context: prerequisites, error conditions, and return value info for a transformation tool modifying workbook state.

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 the description compensates with basic parameter semantics (e.g., 'Name of worksheet', 'Starting cell'). However, it lacks detail on formats (e.g., 'A1' notation) and does not explain all parameters beyond the args list.

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 merges a range of cells, with a specific verb and resource. However, it does not differentiate from sibling tools like unmerge_cells or format_range, which could also involve cell merging.

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 guidance on parameter preference (session_id over filepath) and deprecation, but lacks context on when to use this tool vs alternatives like unmerge_cells or prerequisites (e.g., requiring an open workbook).

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