freeze_panes

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

With no annotations, the description carries the full behavioral burden; it does disclose the core effect (everything above and left of the cell stays visible) and the unfreeze path. It does not say whether an existing freeze is replaced, whether the state persists on save, or whether permissions are required for a protected sheet.

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: the first states the operation and its visual effect, the second teaches the address semantics with two compact examples. Every clause earns its place and the definition is front-loaded.

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 three-parameter, side-effecting-but-reversible worksheet view operation with no output schema, the description supplies almost everything an agent needs to call it correctly, including the null-unfreeze convention. Only the replace-existing-freeze and persistence questions are left open.

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 coverage is 100%, so the baseline would be 3, but the description adds real meaning by mapping cell references to outcomes ("A2" freezes the first row, "B2" freezes row 1 and column A), which the schema's bare "e.g. A2" does not convey. Sheet and workbook parameters gain nothing beyond 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?

Specific verb (freeze/unfreeze) plus resource (rows and columns of a worksheet at a cell), and the parenthetical explains the resulting visibility state. No sibling tool touches worksheet panes, so there is no ambiguity to resolve.

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 covers both modes of use — freeze by supplying a cell, unfreeze by the null path — giving a clear operating context. It stops short of naming when to prefer a freeze over, say, set_dimensions or formatting, and states no prerequisites.

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