freeze_panes

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

The annotation destructiveHint=true already signals mutating behavior, and the description's 'Set or clear' is consistent. However, the description adds no additional behavioral context, such as overwriting existing freeze settings, reversibility, or side effects. With the annotation present, the bar is lower, but the description still adds no value beyond the structured annotation.

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 description is a single, efficient sentence with no redundant words. It is front-loaded and easily parseable, which meets the conciseness requirement despite being under-specified.

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 complexity (5 parameters, no output schema, destructive annotation, many siblings), the description is severely incomplete. It does not explain how freeze panes work, which parameter to use for setting vs clearing, or any behavioral implications. It fails to equip an agent to use the tool 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?

Schema description coverage is 0%, and the description mentions no parameters. The tool has 5 parameters (filepath, sheet_name, cell, dry_run, include_changes) that are completely unexplained in both schema and description, leaving the agent with no understanding of how to set or clear freeze panes or what each parameter does.

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 uses a specific verb phrase 'Set or clear' with a clear resource 'worksheet freeze panes'. It unambiguously identifies the operation and distinguishes it from sibling tools like set_autofilter or merge_cells. The double action (set/clear) is explicit.

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?

No guidance is provided on when to use this tool versus alternatives, nor any context about typical scenarios (e.g., keeping header rows visible). The description only states what it does, not when it should be chosen.

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