get_merged_cells

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Get') but does not explicitly confirm no side effects, mention permissions, or error cases. The parameter note adds some context but overall transparency is limited.

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?

Description is concise with a clear first sentence stating purpose, followed by parameter explanations in a list. The note is relevant and placed at the end. Slightly more could be trimmed, but overall efficient.

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 output schema exists (not shown), description need not detail return values. However, it lacks prerequisites such as requiring an open workbook or valid worksheet name. For a simple getter with three parameters, the description is adequate but could be more complete about tool usage context.

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 description coverage is 0%, so the description adds significant meaning by explaining each parameter's purpose: sheet_name as worksheet name, session_id as preferred from open_workbook, and filepath as legacy deprecated. This goes beyond the schema's name and type.

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?

Description clearly states 'Get merged cells in a worksheet' with specific verb and resource. It distinguishes from siblings like 'merge_cells' and 'unmerge_cells' which perform different actions.

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 guidance on parameter usage, recommending session_id over the deprecated filepath. However, it does not explicitly state when to use this tool versus alternatives, though the purpose is clear enough for a simple getter.

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