set_saturation

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

No annotations provided, so the description carries full burden. It only states the value range (1.0 normal, 0.0 desaturated) but does not specify behavior for values outside this range or potential side effects (e.g., does it reset other color settings?). No mention of return value despite output schema existing.

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?

Two concise sentences that front-load the purpose and describe the parameter in a clear, scannable format. Every word adds value, and no redundant information is present.

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 simple single-parameter tool with an output schema, the description is minimally adequate. It explains the core function and parameter meaning. However, it lacks differentiation from siblings (e.g., when to use saturation vs CDL) and does not describe the return value or side effects, which could be important for an agent.

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%, so description must compensate. It explains that 'value' is saturation with normal at 1.0 and desaturated at 0.0. This adds meaning beyond the schema type. However, it does not specify the valid range (e.g., can value be >1 or <0?), leaving ambiguity.

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 'Set saturation', using a specific verb and resource. It distinguishes from siblings like set_exposure or set_gamma by naming the specific parameter (saturation). However, it could be more explicit about the context (e.g., image/video color grading).

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?

No guidance on when to use this tool versus siblings like set_cdl, set_lut, or other color adjustments. No mention of prerequisites or scenarios where saturation adjustment is appropriate. This omission forces the agent to infer usage from the name alone.

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