add_row_group

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

The description discloses that it inserts a matching group-header row at body row 0 with the group expression in the first cell, and that parent_group raises NotImplementedError. This provides clear behavioral context beyond the input schema.

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 main action, and contains no redundant information. Every sentence adds value.

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 or output schema, the description explains the core functionality but lacks details on error conditions, return value, and full parameter descriptions. 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?

The input schema has only 20% description coverage (only group_expression has a description). The description adds an example for group_expression and explains parent_group behavior, but does not clarify the purpose of path, group_name, or tablix_name.

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 states 'Add a row group that wraps the entire current top-level row hierarchy' which is a specific verb and resource. It clearly distinguishes from sibling tools like add_column_group and add_static_row by focusing on row grouping.

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 indicates it operates on the 'entire current top-level row hierarchy' and notes that parent_group is reserved for future use, implying only top-level grouping is possible. However, it does not explicitly mention alternatives like add_column_group for column grouping.

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