Set Report Theme

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

Annotations indicate idempotentHint=true, and the description adds some behavioral detail (hex colors, dataColors 6-12, visualStyles keying). However, it does not disclose side effects, authorization needs, or what happens to existing theme settings. The description adds value beyond annotations but remains limited.

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 very short (one sentence plus fragments), which is concise but lacks structure. It front-loads the core action but omits important details. Could be improved with clearer separation of parameter constraints.

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 9 parameters, no output schema, and only idempotentHint annotation, the description is incomplete. It does not explain the 'name' parameter, return values, or the effect of other color parameters. A more detailed description is needed for effective tool use.

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 0% schema description coverage, the description must add meaning. It provides some guidance for dataColors (6-12 values) and visualStyles (keyed by visualType or '*'), but ignores other parameters like name, background, foreground, etc. Partially compensates but insufficient for the 9-parameter schema.

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 states 'Apply a custom JSON theme' which is a clear verb+resource, but it is too vague to differentiate from siblings like pbir_apply_theme or pbir_set_report. It lacks specificity about what exactly the theme modifies.

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 no guidance on when to use this tool versus alternatives (e.g., pbir_apply_theme, pbir_set_report). It does not mention prerequisites, context, or exclusion criteria.

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