update_frozen_column_count

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

Annotations already provide idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds context about horizontal scroll visibility and the fact that the first N columns from the left are frozen. It does not contradict annotations and adds value beyond them.

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 with no extraneous information. The first sentence declares the action and resource, the second clarifies the behavior. Every word earns its place.

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?

The description explains the behavior clearly and is complete for a simple tool. However, it does not specify constraints on frozenColumnCount (e.g., maximum value based on number of columns), and there is no output schema, so return value is not described. Still, it covers the essential context.

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 input schema has 100% description coverage for all 4 parameters. The tool description does not add additional meaning beyond the schema; it only restates the concept. Baseline 3 is appropriate as schema does the heavy lifting.

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 ('Set the frozen-column divider position') and the resource ('grid view'), with an additional explanation of the effect. It distinguishes from sibling tools like set_view_columns or reorder_view_fields by focusing specifically on frozen column 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 implies when to use this tool (to freeze columns), but it does not provide explicit when-not or alternatives. Sibling tools that modify columns (e.g., set_view_columns, move_visible_columns) are not contrasted, leaving the agent to infer usage context.

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