pivot_text_values

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

Despite having no annotations, the description transparently discloses key behavioral traits: the use of Text.Combine aggregation, joining colliding values with a delimiter (default ", "), and appending a step to the table's M query. This goes beyond basic operation and helps the agent anticipate side effects.

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 (three sentences), front-loaded with the core purpose, and every sentence adds meaningful information without redundancy. It strikes an ideal balance between brevity and informativeness.

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 tool has 6 parameters, no annotations, and no output schema, the description adequately covers the key behavioral aspects and side effects. It could mention prerequisites like session or table context, but the current level of detail is sufficient for an agent to invoke the tool correctly in typical scenarios.

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 covers 67% of parameters with descriptions. The description adds semantic value by clarifying the aggregation mechanism (Text.Combine), the delimiter default, and the behavior for colliding values, which enriches understanding of the delimiter and valueColumn 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 the tool pivots TEXT values using Table.Pivot with a Text.Combine aggregation, explicitly distinguishing it from the default pivot which errors on text values. The verb 'Pivot' and resource 'TEXT values' are specific, and the mention of the default pivot error sets it apart from sibling tools like pivot_column.

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 clear context for when to use this tool: when pivoting text values that would otherwise cause the default pivot to error. It doesn't explicitly name alternative tools or exclusions, but the rationale is clear enough for an agent to infer suitability.

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