sheets_merge_cells

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

The description does not mention that merging cells keeps only the top-left cell's value and discards others, nor does it indicate that the operation is irreversible. With no annotations, the description should disclose these behavioral traits.

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 sentence, very concise. However, it is too minimal; a bit more detail (e.g., behavior, parameter hints) could be added without losing conciseness.

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 tool's complexity (data loss, merging behavior) and lack of schema documentation, output schema, or annotations, the description is severely incomplete. An agent cannot safely use this tool without guessing critical details.

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 description adds no meaning beyond the schema. Parameters like 'mergeType' with enum values (MERGE_ALL, MERGE_COLUMNS, MERGE_ROWS) are not explained, and 'range' format is unspecified. Schema coverage is 0%, but the description does not compensate.

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 cells') and the resource ('Google Sheet'), which is specific and distinguishes it from sibling tools like 'sheets_unmerge_cells'.

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 on when to use this tool, prerequisites (e.g., cells must be adjacent), or critical warnings about data loss. The description does not help an agent decide between this and similar tools like 'sheets_format_cells'.

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