set_view_columns

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

The description explains the exact behavior (hides everything then shows selected columns) and the effect of optional freeze. Annotations indicate idempotentHint=true, and the description does not contradict any annotation. It adds the 'one-shot' reset context.

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 extremely concise with two short sentences. The first sentence states the core functionality, and the second provides usage guidance. 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?

For a tool with 5 parameters (all well-documented in schema), no output schema, and clear annotations, the description covers the main behavior and usage context. The 'debug' parameter is mentioned in schema but not in description, but the description's completeness is adequate for agent selection.

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, so the description does not need to elaborate much. It briefly mentions 'optional freeze' which aligns with frozenColumnCount. No additional parameter info is necessary given the schema completeness.

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 tool's action as a one-shot view-column reset, explaining that it hides all columns then shows only the specified ones in order. It distinguishes itself from the sibling tool 'show_or_hide_view_columns' by contrasting the use case.

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 explicitly states when to use this tool ('fresh view setup or full layout rewrites') and when to use an alternative ('show_or_hide_view_columns' for toggling specific columns without resetting). This provides clear decision criteria.

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