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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit for adding return composition: 11 steps, hue preserved, hex plus contrast on white and black plus recommended text color per step — meaningful since no output schema exists. It could still note determinism or that the base color is echoed as one of the steps.

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 sentences: trigger conditions first, output shape second, example last. Every sentence carries information an agent needs and nothing is repeated from the schema or annotations.

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 two-parameter, read-only, no-output-schema tool, the description supplies the trigger context, the full return content, and a working example. Nothing an agent needs to invoke it correctly is missing.

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 goes beyond by supplying a concrete invocation example with both parameters populated ({"color": "#ff5a1f", "name": "brand"}), which shows the optional name in context. It does not explain format tolerance (hex vs named colors) beyond the schema's own example.

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?

States a specific verb (build) and resource (a 50-950 color palette / 11-step ramp) from a single base color, immediately separating it from siblings like swatch_check_contrast or swatch_convert_color.

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 opening clause enumerates concrete user intents ('palette, shades, tints, a design-token scale or a Tailwind-style 50 to 950 ramp') that should trigger this tool, which is strong routing guidance. It stops short of naming the sibling tools or stating when NOT to use it (e.g. single-pair checks belong to swatch_check_pairs).

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