Set sheet layout

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false). The description contributes beyond them by explaining that autofit estimates widths from value text length, but says nothing about permissions, what happens to unspecified fields, or overlap with existing formatting.

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 primary purpose is front-loaded in one sentence, followed by targeted parameter notes. No filler sentences, though the freeze_panes/auto_filter notes partially duplicate schema text rather than fully earning their space.

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?

With a mutation tool whose safety profile is covered by annotations and whose return values are covered by an output schema, the description supplies the layout semantics an agent needs. The gap is the lack of when-to-use routing against siblings like format_range.

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 67%, so the schema documents most fields. The description still adds value by explaining autofit's estimation behavior and by giving the 'B2' freeze-panes case, which the schema only partially covers. Minor repetition of the schema's 'A1:F100' auto_filter example keeps this from a 5.

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 opening sentence states a specific verb ('Set') and enumerates the exact layout resources it controls (column widths, row heights, frozen panes, auto filter, tab color). It is clearly distinguishable from format_range or insert_rows_or_columns by scope, though it never names an alternative to sharpen the contrast.

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?

Usage is implied by the enumerated layout attributes, but there is no explicit guidance on when to choose this tool over format_range (styling) or insert_rows_or_columns (structural changes). No prerequisites or exclusions are stated.

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