pbi_list_instances

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

Without annotations, the description must bear the full burden of behavioral disclosure. It indicates a non-destructive list operation, but lacks details on caching, freshness, or side effects.

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?

A single sentence conveys the essential information with no extraneous words, perfectly front-loading the purpose.

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?

Given the tool's simplicity (zero parameters, low complexity), the description is adequate. An output schema exists, so detailed return value documentation is not required.

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?

There are no parameters, so the description cannot add value beyond the schema. Baseline 4 applies due to perfect schema coverage.

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 explicitly states 'List discovered Power BI Desktop instances without forcing a connection,' clearly identifying the tool's function and differentiating it from connection-oriented siblings like pbi_connect.

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 phrase 'without forcing a connection' implies safe, non-disruptive usage, but does not explicitly state when to choose this over alternatives or mention exclusions.

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