pbi_set_column_visibility

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

No annotations are provided, so the description carries the burden. It discloses that mode='both' is temporarily disabled and explains the live/pbip constraints ('Power BI Desktop abierto/cerrado') and that only one destination would be applied. This is valuable behavioral context beyond the schema.

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 concise and front-loaded with the purpose, then explains the key mode limitation. Three sentences with no fluff, each earning its place. Slightly formal but efficient.

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 an output schema present, return values are not the description's responsibility. It covers the critical operational nuance (mode restrictions) and gives an example use case. It lacks explicit notes on effects on reports or persistence, but for a visibility toggle with output schema, it is sufficiently complete.

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?

The description adds significant meaning for the 'mode' parameter (live/pbip/both and their constraints), but does not elaborate on 'table', 'column', 'hidden', or 'request_id'. Given schema coverage is 0%, the description compensates only partially, leaving the other parameters' semantics to their names and defaults.

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 tool's function: 'Oculta o muestra una columna del modelo' (Hides or shows a column), with a concrete example ('ocultar columnas de ID'). It also distinguishes from sibling pbi_hide_columns by explicitly covering both hide and show actions.

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?

Provides explicit guidance on mode selection: mode='both' is disabled, 'live' requires Power BI Desktop open, 'pbip' requires it closed, and instructs to choose 'live' or 'pbip'. This offers clear context for correct usage, though it does not compare directly to alternative tools.

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