dynamic_unpivot_other_columns

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

With no annotations present, the description carries the full burden. It discloses a key behavioral trait: the unpivot set is derived at evaluation time, causing new columns to auto-unpivot. It also states that it appends one step to the table's M query, providing side-effect information. It does not mention reversibility or error conditions, but the disclosed behaviors are valuable.

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, front-loaded with the core purpose, and every sentence adds meaningful content. 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?

For a transformation tool with no output schema, the description covers the essential aspects: what it does, the dynamic behavior, the meaning of keepColumns, and the side effect on the M query. It misses potential details about partitionName behavior or error cases, but these are minor given the overall clarity.

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 already describes keepColumns and partitionName, and the description adds little beyond that. It reiterates that keepColumns is comma-separated and explains its role, but this is already in the schema. With 50% schema coverage, the description could compensate, but it does not add new parameter-level details for the other parameters.

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 that the tool unpivots every column not in keepColumns, which is a specific verb and resource. It also distinguishes from sibling tools by highlighting the dynamic derivation from Table.ColumnNames at evaluation time, setting it apart from static unpivot alternatives.

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 this tool: when new attribute columns may be added later and should auto-unpivot. However, it does not explicitly mention alternatives or provide when-not-to-use guidance. This gives clear context without exclusions, so a 4 is appropriate.

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