hue_saturation

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only says 'apply', implying a mutation, but gives no details about reversibility, parameter ranges, or impact on the target layer. This is minimal and largely non-transparent.

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 a single, concise sentence with no fluff, but it is under-specified. It is front-loaded but lacks necessary content, so it is not optimally concise—it is simply short.

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 has 4 required parameters, no annotations, and a minimal description, the description is insufficiently complete. It does not explain the role of layer_id, value ranges, or what the adjustment does to the image or layer. The presence of an output schema does not compensate for the lack of behavioral and parameter context.

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 schema has no descriptions (0% coverage), and the description only mentions the names of the parameters (hue, saturation, lightness) without explaining their meaning, ranges, or units. It adds no practical value beyond the schema's property names.

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 applies a hue, saturation, and lightness adjustment, which is a specific verb-resource combination. It is distinguishable from sibling tools like brightness_contrast and desaturate, though it does not explicitly name them as alternatives.

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?

Usage is implied by the description: it is for applying basic hue/saturation/lightness adjustments. However, there is no explicit guidance about when to choose this tool over similar adjustment tools, nor any prerequisites or layer targeting advice.

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