merge_cells

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

No annotations are present, so the description carries the full burden. It discloses auto-backup behavior, the backup=False nuance, atomic validated saving, and refusal when the document is open in Word. This is strong for a mutation tool, though it does not explicitly state what happens to cell contents during the merge, and the 'skip rotation only' wording is somewhat ambiguous.

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 compact and front-loaded: the core action comes first, followed by backup behavior and a safety constraint. Every clause contributes information, and there is no filler or redundant repetition of the tool name.

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?

For a 7-parameter mutation tool with no annotations and an output schema, the description covers the essential context: operation semantics, coordinate inclusivity, backup behavior, save safety, and a refusal condition. Minor gaps remain, such as table_index indexing convention and the precise meaning of 'rotation only', but nothing critical for invoking the tool correctly is missing.

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?

With 0% schema description coverage, the description compensates meaningfully by explaining that coordinates are grid-based and inclusive, and by clarifying the backup parameter's effect. file_path and table_index are left to their self-explanatory names, but the most ambiguous parameters receive useful semantic grounding.

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') and resource ('rectangle of cells') and adds an explicit semantic detail ('grid coordinates, inclusive'). This clearly differentiates it from sibling operations like unmerge_cells or set_cells without needing to inspect schemas.

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 gives useful operational context and a hard refusal condition (documents open in Word), but it does not explicitly explain when to prefer this tool over alternatives such as unmerge_cells or set_cells. The intended use is implied by the action and first clause, but there is no explicit routing or when-not-to-use guidance beyond the Word-open refusal.

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