build_palette

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

No annotations are provided, so the description carries the full burden. It discloses key behavior: the output is 11 steps, contrast against white and black is precomputed, and CSS custom properties are included. It does not discuss side effects or edge cases, but the operation is described as a pure return, so nothing is misleading.

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?

Three tight, substantive sentences: what it does, what it returns, and when to use it. There is no filler and no repetition of schema fields.

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 two-parameter generator, the description covers the operation, color space, number of steps, contrast behavior, output artifacts, and the alternative to avoid. The explicit return summary compensates for the lack of an output schema.

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 baseline is 3. The description reinforces that a seed colour drives generation, but it does not add format or default details beyond what the schema already provides.

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 names the exact operation ('Build a perceptually even colour ramp') and method ('from one seed colour, in OKLCH'). It clearly identifies this as the palette-generation tool among siblings and even contrasts it with hand-picking hex values.

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?

It gives explicit context: use this instead of hand-picking hex values, which produce uneven ramps. However, it does not explicitly mention sibling-tool exclusions such as suggest_pairing or check_contrast.

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