move_visible_columns

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

Provides behavioral details beyond annotations, such as the API preserving relative order of column IDs and the debug parameter's effect. Does not contradict annotations, though return format is not described (acceptable given no output schema).

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, front-loaded with purpose, no wasted words.

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?

Covers purpose, usage guidelines, and a behavioral caveat. Lacks explicit mention of preconditions or return value, but is adequate for the tool'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?

All parameters have thorough descriptions in the schema itself, so the description adds minimal parameter-specific meaning beyond reinforcing the visible-only context. Baseline 3 is appropriate for 100% schema coverage.

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?

Description clearly states the action (move columns to a new position in the visible-only index) and distinguishes from two sibling tools by explaining their different scopes.

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?

Explicitly names alternatives (`reorder_view_fields` and `move_overall_columns`) and describes their different ordering semantics, guiding when to use this tool.

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