remove_columns

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

The description discloses a meaningful behavioral detail: it appends Table.RemoveColumns to the table's M query. However, it does not mention side effects, reversibility, error handling, or permission requirements, and with no annotations, the description carries the full burden but leaves these gaps.

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 brief and front-loaded with the core action, but the phrase 'Power Query Remove Columns' is somewhat redundant with the tool name, and the 'columns is comma-separated' repeats schema information. Still, it contains no fluff and is well-structured overall.

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 the lack of annotations and output schema, the description provides the essential behavior and mechanism, which is adequate for a simple tool. However, it omits usage context, parameter explanations for sessionId and table, and any side-effect or error information, leaving the description only partially 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 has only 50% parameter description coverage, and the description does not compensate. It restates that 'columns' is comma-separated (already present in the schema) and provides no explanation for sessionId or table, which remain undocumented.

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 'drop columns' and specifies the underlying M operation (Table.RemoveColumns), making the action unambiguous. It distinguishes itself from sibling operations like renaming or selecting columns by focusing specifically on removal.

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 is given on when to use this tool versus alternatives such as select_columns or rename_columns. The description only explains what the tool does, not the context or conditions under which it should be chosen.

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