pbi_set_column_visibility

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses important behavioral constraints: 'live' requires Power BI Desktop open, 'pbip' requires it closed, and mode='both' is disabled. This explains why only one destination can be applied per call and clarifies the default mode's prerequisite.

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 paragraph of about 80 words, front-loaded with the purpose statement. It covers essential mode behavior and prerequisites without redundancy, though it could be structured more clearly.

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's mode complexity is thoroughly addressed: the disabled 'both' option, prerequisites for 'live' and 'pbip', and 'auto' behavior are all explained. With an output schema present, return-value documentation is unnecessary, but request_id remains unexplained.

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?

With 0% schema description coverage, the description compensates for the 'mode' parameter by explaining its values and default behavior. However, it leaves 'table', 'column', 'hidden', and 'request_id' without additional semantics, though most are self-explanatory from names/types.

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 'Oculta o muestra una columna del modelo', which is a specific action (hide/show) on a model column. It implicitly differentiates from the sibling tool pbi_hide_columns by including 'muestra' (show) and singular 'columna', making its scope clear.

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 provides detailed guidance on mode selection ('live' vs 'pbip' vs 'auto') and warns that 'both' is temporarily disabled due to conflicting prerequisites. However, it does not explain when to choose this tool over alternatives like pbi_hide_columns, so tool-selection guidance is implied at best.

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