merge_cells

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

With no annotations, the description must disclose behavioral traits, but it fails to mention that merging cells is destructive (data in non-top-left cells may be lost), or any authorization requirements. The brief mention of gridSpan and vMerge hints at implementation but doesn't clarify observable impact.

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 (two sentences), but brevity comes at the cost of completeness. While it avoids redundancy, it fails to provide critical context, making it less useful than an equally short but more informative description.

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 presence of 5 required parameters and an output schema (though not shown), the description should at least explain the range specification and merge behavior. The current text is too sparse for an AI to reliably use the tool without additional context from the schema or annotations.

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%, and the description does not explain any of the five parameters (table_index, start_row, start_col, end_row, end_col). The terms gridSpan and vMerge are mentioned but not mapped to the input schema, leaving the AI without guidance on how to specify the range.

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 (merge) and resource (rectangular range of cells), and hints at horizontal/vertical merge behavior via 'gridSpan' and 'vMerge', which distinguishes it from sibling tools like 'split_table' or 'modify_cell'. However, it could be more explicit about the scope.

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 is provided on when to use this tool versus alternatives like 'split_table' or 'modify_cell'. There is no mention of prerequisites, such as whether cells must be empty or contiguous, leaving the AI to infer context.

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