unmerge-excel-range

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

Annotations indicate destructiveHint=true, and the description adds that there is 'No request body' and it is the inverse of merge. However, it does not disclose what happens to the data in merged cells (e.g., only top-left value retained) or permissions needed.

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?

Description is concise (one sentence plus a tip). It is front-loaded with the purpose. Could be slightly more structured by integrating the tip into the main sentence, but overall efficient.

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 mutation tool with destructive hint and no output schema, the description adequately states the core action but omits consequences (data retention, required permissions). It is minimally complete but could be improved.

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?

Input schema covers all 6 parameters with descriptions (100% coverage), so baseline is 3. The description does not add any additional meaning or context to the parameters beyond what the schema provides.

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 ('Unmerge') and the resource ('any merged cells within the given range'), and distinguishes it from the sibling 'merge-excel-range' by noting it is the inverse.

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?

Provides a contrast with 'merge-excel-range' but does not offer guidance on when to use this tool over other range-modifying siblings like 'clear-excel-range' or 'format-excel-range'. No explicit when-to-use or when-not-to-use.

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