xlsx_merged_cells

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

Annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) are already present. Description adds details about what is returned (master value, range, span, kind heuristic) and notes the free tier cap. No contradiction with 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?

Well-structured with problem statement, tool purpose, comparison, usage guidelines, and limitations. Slightly lengthy but front-loaded with key information. No wasted sentences.

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 no output schema, description explains return fields (value, range, span, kind). Use cases and limitations are covered. Schema has 2 params with clear types. Annotations provide safety cues. Complete for a listing 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?

Schema has 2 parameters with 0% coverage. Description does not explain file_b64 or options (limit, sheet) beyond what schema provides. While schema is self-explanatory, description could add context (e.g., file format, how to pass base64). Adequate but missing added value.

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 tool lists merged-cell regions with master-cell value, range, span dimensions, and kind heuristic. It distinguishes from siblings by noting no other tool surfaces merges with master values, and explains the value over pandas and openpyxl.

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?

Explicit USE WHEN (parsing report templates, dashboards, auditing) and DO NOT USE WHEN (if only need cell values, use xlsx_read). Provides clear context and alternatives.

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