set_view_columns

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

The description reveals behavioral traits beyond annotations: it explains the internal process of hiding all columns first then showing specified ones, and mentions the optional frozen-column divider. Annotations indicate idempotentHint=true, which aligns with 'one-shot'. No contradictions.

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 succinct sentences. The first states the precise action; the second gives a practical example. No unnecessary words or repetition.

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 is complete for the primary functionality. It covers the main effect and use case. The debug parameter is not mentioned, but that is a minor omission and does not hinder overall understanding.

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 100%, so baseline is 3. The description adds meaning by explaining that visibleColumnIds determines both order and visibility, and frozenColumnCount sets the divider. It clarifies the effect of parameters beyond schema descriptions.

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 explicitly states the tool's action: 'One-shot view-column setup. Hides every column in the view, then shows only visibleColumnIds in the order given (left-to-right), then optionally sets the frozen-column divider.' It clearly distinguishes from sibling tools like show_or_hide_view_columns and move_visible_columns.

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 provides a clear use case: 'Use this to turn a brand-new view from "all 168 fields visible" into a curated layout in a single tool call.' This implies when to use it (initial setup) and contrasts with incremental tools, though it does not explicitly list alternatives.

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