unmerge-excel-range

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

The description adds context by stating 'No request body' and that it is the inverse of merge, but annotations already indicate destructiveHint=true and readOnlyHint=false. The description aligns with annotations and provides minimal additional behavioral insight beyond the annotations.

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 relatively concise but includes a redundant 'Invoke action unmerge' that restates the tool name. The tip is helpful, but the structure could be more direct.

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?

The description lacks information about the return value or response, especially given no output schema. It does not explain what happens after unmerging or any side effects beyond the hint, which leaves the agent without complete context for a mutation tool.

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?

The input schema has 100% description coverage for all 6 parameters, so the description does not need to add parameter details. The description only mentions 'No request body', which does not add meaning beyond what the schema already 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 'Unmerge any merged cells within the given range back into individual cells' which specifies the verb (unmerge) and resource (Excel range), and distinguishes it from the sibling 'merge-excel-range' by saying 'Inverse of merge-excel-range'.

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 a clear tip on when to use the tool (to unmerge merged cells) and notes it is the inverse of merge-excel-range, implying the alternative. However, it does not explicitly state when not to use it or address prerequisites.

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