set_page_visibility

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

With no annotations provided, the description carries the burden and does well. It discloses that hidden pages remain in the file and functional, that viewers in Power BI Service do not see the tab, and that hidden=false reverts the visibility—offering clear behavioral expectations.

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 concise sentences with front-loaded purpose. Every sentence adds value: the first states the action, the second explains the effect and reversible nature. No redundancy or filler.

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?

For a simple three-parameter tool with no output schema, the description is sufficiently complete: it explains the operation, the impact on viewers, and the use case. The only minor gap is the undocumented reportSessionId, but this is a common session identifier and does not severely hinder usage.

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 only 33%; only pageName has a description. The description clarifies the hidden parameter's semantics ('hidden=false shows it again') but does not explain reportSessionId, leaving a required parameter under-documented. Partial compensation only.

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 purpose with a specific verb and resource: 'Hide or show a report page (the tab).' It also explains the distinction between hiding and deleting, which helps differentiate it from page deletion or reordering tools.

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 a clear use case: 'use it to keep a page out of a published report.' It implies the appropriate context (publishing) and the effect on viewers, but does not explicitly mention alternative tools for other visibility types (e.g., visuals, mobile).

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