pbi_apply_style_preset

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

With no annotations provided, the description carries the full burden. It mentions 'one-shot' and the effect of wallpaper_fit, but fails to disclose whether the tool modifies the file in place, requires permissions, or any side effects. The presence of an 'output_path' parameter implies potential file creation, but this is not stated.

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 short but includes some redundancy (e.g., listing enum values inline). The sentence 'See module docstring for the full flow.' is a weak reference that suggests the description is incomplete. It could be more self-contained.

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 complexity (7 parameters, no schema descriptions, expected output not explained), the description is insufficient. It does not clarify the return value (despite having an output schema), the effect of 'custom_spec', or how 'pages' filtering works. The agent would need additional context to use the tool correctly.

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 input schema has 0% documentation coverage and 7 parameters. The description only explains 'wallpaper_fit' in detail (enum values and default behavior). No information is provided about 'preset', 'pages', 'custom_spec', 'output_path', or 'wallpaper_path'. This leaves the agent guessing about critical 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 clearly states the tool's function: 'Apply a one-shot visual style preset to an existing .pbix.' It uses a specific verb-resource pair and distinguishes from siblings like pbi_apply_design or pbi_apply_theme by mentioning 'visual style preset' and 'one-shot'.

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 guidance on the optional 'wallpaper_fit' parameter and its default behavior, but it does not explicitly state when to use this tool over alternative tools such as pbi_apply_format_preset or pbi_apply_theme. The reference to 'See module docstring' is insufficient for in-context usage guidance.

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