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

With no annotations, the description carries the burden itself and does decent work: it discloses the deterministic structure (10 levels, 500 anchors the base), that each step ships measured white-text and black-text contrast values, and that output shape is selectable. It does not say whether the contrast figures are WCAG ratios or confirm the tool is a pure, side-effect-free computation.

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 front-loaded sentence opens with the generating action and the scale's range, then adds contrast output and format options in a tight second clause. Nothing is redundant with the schema text.

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 generator with no output schema, the description covers the main things an agent needs: what is produced, how levels are anchored, what accompanies each level, and what formats exist. Minor omissions are the exact level keys and the meaning of the contrast numbers.

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 100%, so both parameters are already documented, including the format enum and its default. The description adds only the '500 equals the base color' anchoring idea, which is output semantics rather than parameter semantics, so the baseline 3 applies.

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 and resource: generate a 10-step 50–900 color scale from a base color, with 500 defined as the base itself. That is materially more specific than the sibling names alone, but it never names which sibling it differs from (get_palette, darken_palette, suggest_palette all sound adjacent).

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 only implied: use this when you need a full tonal ramp from one seed color. There is no when-not guidance and no statement of how it relates to suggest_palette, darken_palette, or check_contrast, even though the embedded contrast data clearly overlaps with check_contrast's territory.

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