set_column_group_visibility

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

The description discloses that it accepts a Hidden expression and optional toggle, and that it refuses if group_name is on row axis. With no annotations, it covers basic behavior but lacks details on side effects, error handling, or prerequisites (e.g., group must exist).

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 sentences, front-loaded with purpose, and every word adds value. No redundancy or fluff.

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?

Despite no output schema and missing parameter descriptions, the description lacks completeness. It doesn't explain common required parameters, return behavior, or outcomes. An AI agent might not know how to construct path or tablix_name values.

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 0%, so description must compensate. It explains two of five parameters: visibility_expression as 'Hidden expression' and toggle_textbox as 'ToggleItem'. It does not describe path, group_name, or tablix_name, leaving gaps for an AI agent.

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 sets visibility on a column-axis group's TablixMember with a Hidden expression and optional toggle. It distinguishes itself from the sibling set_group_visibility by specifying it only works for column-axis groups, preventing misuse.

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?

It provides explicit guidance: mirrors set_group_visibility but refuses row-axis groups. This tells the agent when to use this vs set_group_visibility. However, it does not mention other related visibility tools like set_detail_row_visibility or set_element_visibility.

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