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

The description goes well beyond the readOnlyHint annotation by explaining the snapping behavior (CIEDE2000 to nearest archive colour), anchor stop preservation, the difference between linear and chroma_preserved interpolation, and that the result already carries rendered palette plus PNG, PDF, ASE, JSON and CSS downloads. It also warns against presenting source anchors as recommendations, which is crucial behavioral guidance.

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 fairly long but every sentence earns its place: core mechanism, interpolation choices, output forms, use cases, delivery behavior, and a critical customer-facing instruction. The most important facts are front-loaded, and the cautions are placed at the end where they are still actionable.

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 output schema exists, the parameter schemas are fully described, and the tool has 6 parameters, this description is highly complete. It covers algorithm behavior, output formats, download carrying, and the exact follow-up action needed when an agent chooses its own palette. Nothing material is missing for correct invocation and interpretation.

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 the baseline is 3. The description adds value by explaining the interpolation paths beyond enum labels, mapping output_format to actual outputs ('stop array, CSS linear-gradient string, or SVG swatch bar'), and describing what 'snapping to archive colours' means for anchors and interpolated stops. This enriches the schema without replacing it.

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 and resource: it generates a perceptually smooth, lab-interpolated gradient between 2-5 archive anchor colours, with each stop snapped to a real archive colour. This is far more than a restatement of the title and clearly distinguishes the tool's core function from siblings like palette_compare or palette_finalize.

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 description gives explicit use cases: 'Use for design briefs, colour journey visualisations, and gradient systems.' It also gives a strong follow-up rule: if the agent chooses its own final palette, it must call palette_finalize with those exact colours. It does not explicitly name excluded alternatives, but the context and follow-up instruction are clear enough.

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