set_group_visibility

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

With no annotations, the description carries full burden. It states it sets visibility but does not disclose if the operation is destructive, whether it validates the expression, or what side effects occur. It mentions accept parameters but not behavioral outcomes.

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 a single, front-loaded sentence that conveys the core action and key parameters efficiently. However, it could benefit from brief structured details for clarity.

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?

With 5 parameters, no output schema, and no annotations, the description is insufficient. It omits details on required parameters like path, tablix_name, and group_name, and does not explain the toggle behavior or return value.

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 visibility_expression as a Hidden expression and toggle_textbox as an optional toggle item, adding meaning beyond the schema. However, it does not clarify path, tablix_name, or group_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 clearly states it sets visibility on a group's TablixMember, distinguishing it from sibling tools like set_column_group_visibility or set_detail_row_visibility. It explicitly mentions the Hidden expression and optional ToggleItem, making the action specific.

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?

No when-to-use or when-not-to-use guidance is provided. There is no comparison to alternative visibility tools among siblings. The description does not indicate prerequisites or context needed for invocation.

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