concatenate_with_group_by

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

With no annotations, the description carries the burden of disclosing behavior. It states that the tool 'Appends one step to the table's M query' and 'Collapses each group's textColumn values into one delimited string', which provides some insight. However, it omits details about reversibility, error conditions, or permissions, making it moderately transparent.

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 succinct, front-loading the main purpose and including only relevant details. Each sentence earns its place, covering functionality, parameter guidance, and side effects without 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 is fairly complete. It explains what the tool does, how it operates (grouping, delimiter), and the side effect on the M query. Optional parameters like partitionName are not mentioned but are covered in the schema, so the description is adequate.

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 71%, and the description restates what is already in the schema: 'keys is comma-separated' and delimiter defaults. It does not add meaningful new semantics for parameters beyond the schema, so a baseline score of 3 is appropriate.

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's purpose: 'Concatenate text within groups' with a specific action and resource. It also distinguishes itself by referencing 'the inverse of split-to-rows' and naming the underlying operations (Table.Group + Text.Combine), making its role clear among sibling tools.

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 useful context by noting it is the inverse of split-to-rows, implying when this tool should be used. However, it does not explicitly mention situations to avoid or name alternative tools, so it lacks exclusions but is not misleading.

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