Adjust Color

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-mutating, repeatable operation. The description adds no behavioral details beyond the schema, such as how relative vs absolute adjustment behaves or whether the result is returned inline. With annotations covering safety, a 3 is appropriate.

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?

A single sentence of seven words that front-loads the action and resource with zero waste. It is appropriately sized for the tool's simplicity.

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, well-annotated adjustment tool with full schema coverage and no output schema, the description is minimally adequate. It is missing usage context relative to siblings and any note on return behavior, but the annotations and schema carry most of the burden.

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 description coverage is 100%, so the parameter details (mode enum, color format examples, amount semantics, relative flag default) are fully documented in the schema. The description adds no parameter meaning beyond what the schema provides, so baseline 3 is correct.

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 a specific verb (Adjust) and resource (color properties) and enumerates the three adjustable properties (lightness, chroma, hue). It is clear what the tool does, though it does not differentiate itself from siblings like colors_scale or colors_mix beyond naming the properties.

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?

There is no guidance on when to use this tool versus alternatives such as colors_scale, colors_mix, or colors_batch_adjust. The description merely restates the purpose without any context about selection criteria or prerequisites.

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