move_column

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

Discloses that it appends Table.ReorderColumns to the table's M query, which reveals implementation behavior. However, with no annotations, it doesn't disclose side effects like session state changes, reversibility, or error conditions.

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?

Four short clauses, front-loaded with purpose. 'Power Query Move Column' is a label, but the rest is direct. 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?

Covers core behavior and key constraint, but misses usage guidance, return behavior, and session/partition semantics. For a tool with 6 params and no output schema, this is somewhat sparse.

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 schema already describes position and refColumn; the description repeats these. It doesn't explain table or sessionId, though those may be common. Adds no significant meaning beyond schema.

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 it repositions a column in Power Query and mentions the underlying Table.ReorderColumns operation. It doesn't explicitly differentiate from sibling tool 'reorder_columns', but the specific positional parameters make its purpose clear.

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?

No guidance on when to use this tool versus reorder_columns or other column manipulation tools. The only guideline is a parameter constraint (refColumn required for before/after), which is about parameter usage, not tool selection.

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