preview_white_balance

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

With no annotations, the description conveys that it renders multiple previews with Kelvin temperature reference, but it lacks details on side effects, performance, output format, or limitations beyond RAW files.

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 with a front-loaded purpose, but the param list is redundant with the schema and adds clutter, making it slightly less concise.

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 no output schema, the description partially explains that multiple renders are produced with Kelvin reference, but it omits details on return format (e.g., images vs. JSON) and how outputs are presented.

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?

Schema coverage is 0%, but the description only lists parameter names without explaining valid values (e.g., preset options) or how max_width affects output, adding minimal value beyond the 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 clearly states the tool previews different white balance presets on a RAW file for comparison, distinguishing it from other preview tools like preview_raw or preview_with_adjustments.

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 for choosing white balance but does not explicitly state when not to use it or mention alternative tools like preview_raw or preview_lut.

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