move_visible_columns

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

No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds key behavioral context: the API preserves existing relative order of supplied IDs, and warns about the need for multiple calls for custom sequencing. Also notes the debug parameter for diagnostics.

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?

Extremely concise: two short sentences plus a warning line. Every sentence adds value—purpose, differentiation, and behavioral nuance. No fluff.

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 covers the core behavior, usage guidance, and a critical API caveat. No output schema exists, but the debug parameter hints at response content. Could mention that the change is persistent or any error conditions, but overall sufficient for a focused mutation tool with good annotations.

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 description coverage is 100% and already includes thorough parameter descriptions (e.g., the caveat on columnIds). The tool description does not add new meaning beyond the schema, so baseline of 3 is appropriate.

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 states a specific verb ('Move') and resource ('columns by visible-only index'), clarifying that index 0 is the leftmost shown column. It explicitly distinguishes from the sibling 'move_overall_columns' by contrasting visible-only vs full column order.

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?

Clear guidance on when to use: 'Use when you want to position relative to what the user sees.' Directly names the alternative 'move_overall_columns' for different needs. Also warns about the API preserving relative order and advises one call per column for custom sequences.

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