Get Merge Info

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

readOnlyHint already flags this as safe, and the description adds the return behavior: JSON containing is_merged and, when true, the full merged area's address. No side effects or contradictions are mentioned.

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 one-sentence purpose is front-loaded, followed by a compact Args list and a short Returns line. Every sentence adds information; no filler or repetition.

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?

For a simple read-only check with three optional parameters and no output schema, the description covers the inputs, the defaults, and the return shape. An agent has everything needed to invoke it correctly.

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 0% schema description coverage, the description fully compensates by explaining workbook (name or path, None = active), sheet (name, None = active), and cell (A1-style reference with an example). Each parameter's meaning is unambiguous.

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 opens with a specific verb and resource: 'Check whether a cell is part of a merged range.' This clearly defines the tool's purpose and distinguishes it from mutating siblings such as merge_cells and 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?

The purpose statement makes the intended use obvious: call this when you need to know if a cell belongs to a merged range. It doesn't name alternative tools or give explicit when-not-to-use guidance, but no close alternative is needed for this inspection operation.

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