pbi_list_themes

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

Annotations already declare readOnlyHint=true, so the description doesn't need to address mutation safety. It adds transparency by detailing what the tool returns—usage scenario, background color, series colors in order (with the rationale that order ensures color-blind-safe distinction), and status colors—which goes beyond the annotated safety profile.

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, with the main point front-loaded and every sentence providing valuable information. It includes the purpose, the returned data, and usage guidance without any 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 zero-parameter read-only listing tool with an output schema, the description thoroughly covers the purpose, output content, and usage context. The added detail about color order and accessibility makes it particularly 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 tool has zero parameters, and schema coverage is 100% (vacuously). Per the rubric, the baseline for 0 parameters is 4, and the description does not need to add parameter semantics because there are none.

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 it lists available report themes with their palettes and purpose, using a specific verb and resource. It also distinguishes itself from theme application tools by emphasizing the use case of proposing a scheme before building.

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?

It explicitly instructs to use the tool to propose a scheme before building, and phrases it as an alternative to deciding for the user. However, it does not explicitly name sibling tools like pbi_apply_theme as alternatives, so it falls short of a full 5.

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