select_columns

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

No annotations are provided, so the description carries the burden. It discloses that the tool appends Table.SelectColumns to the table's M query and drops non-listed columns, providing behavioral context. However, it does not mention reversibility or any permission requirements.

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 with no waste; first sentence states the core action, second provides technical detail and parameter format. The description is well-structured and front-loaded.

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 mutation tool with no annotations and no output schema, the description provides core behavior and table context, but omits details about sessionId, return values, and prerequisites. It is adequate but not exhaustive, making it a minimum viable description.

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 descriptions cover columns and partitionName; description adds that 'columns is comma-separated' and implies 'table' is the table whose M query is modified. sessionId remains undocumented, and no new semantics are added for partitionName 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 the tool keeps ONLY the listed columns in order and drops the rest, referencing Power Query's Table.SelectColumns. This distinguishes it from sibling tools like remove_columns or reorder_columns.

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 explicit when-to-use guidance or alternatives are mentioned. The behavior is clear enough to infer usage, but it does not name alternatives such as remove_columns or reorder_columns, so guidance is implied rather than explicit.

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