duplicate_column

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool appends Table.DuplicateColumn to the M query, which implies a mutation of the table's query. However, it does not disclose whether this is reversible, what permissions are needed, or what effects occur on existing query steps, leaving some gaps for a mutation tool.

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 two sentences long, front-loaded with the tool's name and primary action, and contains no redundant information. Every word contributes to understanding the tool's purpose and mechanism.

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 simple transformation tool with no output schema and no annotations, the description adequately communicates the core behavior and the underlying M query change. It lacks explicit usage guidelines and parameter prerequisites, but the schema fills most structural gaps, and the tool is simple enough that this description is nearly complete.

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 provides descriptions for column, newName, and partitionName (60% coverage), and the description reinforces the meaning of column and newName with 'copy a column under a new name'. It does not add clarity for table and sessionId, which remain undocumented in both schema and description. Overall, the description adds some value but does not fully compensate for the missing parameter documentation.

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 copies a column under a new name, using the specific verb 'copy' and the resource 'column'. It also mentions the implementation detail of appending Table.DuplicateColumn to the M query, which distinguishes it from similar column operations like rename_column or remove_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?

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The 'Power Query Duplicate Column' label gives a general context, but it does not clarify situations where this tool is preferred over other column manipulation tools.

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