set_element_visibility

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

No annotations are provided, so the description must fully disclose behavior. It mentions setting a hidden_expression and an optional toggle, but does not explain what the hidden_expression evaluates to (e.g., true hides, false shows) or any side effects like overwriting. Some behavioral context is given, but incomplete.

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 with no redundant information. It front-loads the primary action and follows with alternatives and an optional feature. 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?

The tool has 4 parameters with no output schema. The description covers the main action and alternatives, but leaves path and element_name unexplained. For a setting tool, more detail on parameter values (especially hidden_expression syntax) would improve completeness.

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 description coverage is 0%, so the description must explain parameters. It describes hidden_expression and toggle_textbox, but does not explain path or element_name. Only half the parameters are clarified, leaving ambiguity about the required inputs.

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 named ReportItems, listing specific item types. It distinguishes from sibling tools by explicitly naming set_group_visibility and set_detail_row_visibility for other cases.

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: for named ReportItem visibility use this tool, for group-level use set_group_visibility, for detail-row use set_detail_row_visibility. Also explains optional toggle_textbox for expand/collapse behavior.

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