sheets_unmerge_cells

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

With idempotentHint=true annotation, the description's scope is narrow. It does not contradict the annotation, but it also doesn't add behavioral details beyond the basic action, such as how it handles a range with partially merged cells or whether it's safe on non-merged ranges. The description is adequate but minimal.

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 a single, concise sentence that is front-loaded with the verb 'Unmerge' and the target resource. Every word earns its place with no unnecessary filler.

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 tool is simple, and the description covers the core function, but it lacks detail on edge cases (e.g., what happens if the range contains no merged cells) and does not elaborate on parameter usage. Given the lack of output schema and minimal annotations, the description is sufficient for basic usage but not fully comprehensive.

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 schema has 0% description coverage, and the description does not explain spreadsheetId or range. While parameter names are self-explanatory to some extent, the description fails to provide any additional meaning or context, leaving parameter semantics solely to the names.

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 exact action ('Unmerge cells') and the resource ('a Google Sheet'), making it distinct from sibling tools like sheets_merge_cells. It leaves no ambiguity about what the tool does.

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 no guidance on when to use this tool versus alternatives, no prerequisites (e.g., checking if cells are merged), and no mention of when not to use it. It only states the function without contextual direction.

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