rename_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.RenameColumns to the M query, which is a concrete behavioral detail. However, it does not mention error conditions, reversibility, or side effects on the data, leaving 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 concise, consisting of two sentences that deliver the core action and format. It is slightly redundant at the start with 'Power Query Rename Columns', but overall it is efficient with no wasted words.

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?

Given no annotations, no output schema, and moderate complexity, the description covers the main action and parameter format but lacks usage guidance, side effects, and any mention of related tools or prerequisites. It is adequate but not comprehensive.

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 coverage is 50%, and the description adds a concrete example for 'renames' (e.g., 'col1:Amount,col2:Region'), going beyond the schema's 'from:to pairs'. However, 'table' and 'sessionId' remain unexplained in both schema and description, so the description only partially compensates.

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 renames columns in a Power Query query by appending Table.RenameColumns to the M query. It also provides the exact format for the 'renames' parameter, which distinguishes it from siblings like 'rename_column' and 'rename_columns_from_mapping'.

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 when to use the tool (to rename columns in a query) but does not explicitly state when not to use it or mention alternatives such as 'rename_column' or 'rename_columns_from_mapping'. No exclusions or comparison with related tools are provided.

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