reorder_columns

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

With no annotations, the description carries the full burden. It discloses that the tool appends Table.ReorderColumns to the M query, indicating a mutating operation, and clarifies the effect on column order. It does not mention failure modes or side effects, but the core behavior is transparent enough.

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 concise and front-loaded with the primary purpose. Each sentence adds useful information: what it does, its effect on the M query, and the format of the order parameter. There is no fluff or redundancy.

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?

While the core operation is described, the tool has no annotations or output schema, and the description leaves table/sessionId/partition semantics unexplained. For a mutating tool with four parameters, this is adequate but not complete, missing error conditions and explicit parameter roles.

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 only 50%, with table and sessionId lacking descriptions. The description adds no meaningful information about these undocumented parameters; it only restates what the order parameter already explains (comma-separated order). It fails to compensate for the gap, so parameter semantics are weak.

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 the tool's function clearly: 'move the listed columns to the front in the given order (remaining columns keep their relative order)', which is a specific and distinct operation from sibling tools like move_column or select_columns. It also mentions the underlying M query append, reinforcing its purpose.

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 implies usage by stating what it does, but it does not explicitly say when to use this tool versus alternatives such as move_column or sort_column_by. There is no mention of when not to use it or any prerequisites, so guidance is only implied.

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