merge-excel-range

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description carries less burden. It adds context by describing the merge behavior but does not explicitly warn about data loss or other implications beyond what the annotations imply.

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?

Two sentences plus a tip: very concise, front-loaded with the action, and no wasted words. Every sentence serves a purpose.

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 covers the essential merge behavior and the 'across' parameter, but lacks details on destructive effects, prerequisites (e.g., range must exist), or connection to sibling 'unmerge-excel-range'. Without output schema, more context would be helpful.

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 88% schema coverage, the baseline is 3. The description adds value by explaining the 'across' boolean in the body parameter, which is the core parameter for merging behavior. Other parameters are already well-described in the schema.

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 it merges cells in a given range into a single cell, explaining the effect of the 'across' parameter. It distinguishes from siblings like 'unmerge-excel-range' by focusing on the merge action.

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 tip 'Useful for building styled headers, banner rows, and report layouts' gives context for when to use the tool. However, it does not explicitly mention when not to use or alternative tools like 'unmerge-excel-range'.

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