pbi_add_custom_visual

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

Beyond the annotations (which are all false), the description discloses that the report's publicCustomVisuals are modified and that Power BI Desktop downloads the visual from AppSource when opening the report. This adds useful behavioral context, though it does not mention permissions or network requirements.

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: the first states the core action and target, the second covers the default behavior and download-side effect. Every sentence earns its place with no 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?

The tool has no required parameters and an output schema, so basic invocation is covered, but the missing parameter semantics and lack of alternative-tool guidance leave gaps. It is adequate for the simple no-argument use case but not fully complete for selecting other AppSource visuals.

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 schema description coverage at 0%, the description carries the full burden but only explains the no-argument case. It does not explain what visual_id values are expected or the purpose of request_id, leaving the agent guessing about both parameters.

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 opens with 'Registra un custom visual de AppSource en el informe (publicCustomVisuals)', a specific verb plus the resource (AppSource custom visual) and target (report). It also clarifies the no-argument default to 'HTML Content', distinguishing it from generic visual creation tools like pbi_create_visual or pbi_add_image_resource.

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 implies usage by stating that without arguments it registers 'HTML Content', which tells the agent when no visual_id is needed. However, it does not explicitly state when to use this tool over siblings such as pbi_create_visual or pbi_create_html_visual, nor does it mention any exclusions.

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