add_column_group

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

Describes insertion of column and header cells, default width, and that parent_group raises NotImplementedError. Without annotations, it carries full burden and does so fairly well, though could mention prerequisites.

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?

Two concise sentences with a third for a key limitation. No wasted words, front-loaded purpose.

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 output schema and no annotations, description provides sufficient context for typical use, covering effect and limitations, though missing parameter details.

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?

Only 20% schema coverage; description explains parent_group limitation and implies group_expression usage but does not explain path, group_name, or tablix_name. Adds some value but insufficient for low coverage.

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 verb 'add' and resource 'column group'. It distinguishes from siblings by mentioning it mirrors add_row_group on the column axis. The effect is explained in detail.

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?

Clear context that it's the column-axis counterpart of add_row_group, but lacks explicit when-not-to-use or alternatives beyond add_row_group.

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