Freeze rows or columns

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds non-obvious behavioral context: freezing is reversible by passing 0, which the annotations do not convey. It still omits whether the freeze persists across sessions or what happens to `tab` when unspecified.

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 short sentences with the primary action front-loaded and the inverse-operation rule second. Zero filler; every clause carries information.

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 5-parameter mutation with no output schema, the description covers the core action and the unfreeze case but is silent on default tab behavior, whether omitted `rows`/`columns` leaves existing freeze untouched, and the fact that only one required parameter exists. Adequate, but not complete for the schema's complexity.

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 only 40%, so the description must carry more weight. It maps meaning onto `rows`/`columns` (counts of header rows/columns) and clarifies that 0 means unfreeze, which the bare integer schema with minimum 0 does not. However, `tab` is undocumented in both schema and description (e.g. default tab, whether it must exist), leaving a real gap.

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?

States a specific verb (freeze) and resource (header rows and/or columns on a tab), which is unambiguous against siblings like insert_rows_or_columns, resize_columns or format_range, none of which freeze panes. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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?

"Use 0 to unfreeze" gives a concrete value-level rule for the inverse operation, which is genuinely useful for selecting the right call. There is no explicit when-not or alternative-tool guidance, but the tool is unique in the sibling set, so the implied usage is clear.

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