sheets_freeze_panes

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

Annotations are absent, so the description carries the full burden. It mentions the visual effect but does not disclose that default values (0) will unfreeze panes, whether existing freeze settings are overwritten, or any side effects. This is a significant gap for a mutating tool.

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?

One sentence that is clear and front-loaded with the action and purpose. Every word contributes value with no redundancy.

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 annotations and a minimal schema, the description provides the core idea but omits critical details about parameter meanings and the replace/clear behavior. The output schema exists, reducing the need for return-value explanation, but the tool still requires more guidance for correct invocation.

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?

The description adds meaning by associating 'header rows' with frozen_rows and 'header columns' with frozen_columns. However, it does not explain that these are counts or that 0 means no freeze. Schema coverage is 0%, but the baseline is partially met because the parameter names and defaults in the schema are self-evident.

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 action (freeze) and the resource (header rows/columns), and explains the benefit (stay visible while scrolling). It distinguishes this from other spreadsheet operations by focusing on the panes-freezing behavior.

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 implicitly provides usage context by specifying the intended scenario (keeping headers visible during scrolling). It doesn't explicitly mention alternatives, but there are no sibling tools for freezing panes, so exclusion is unnecessary.

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