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

Annotations only declare readOnlyHint=true. The description adds substantial behavioral detail beyond this: nearest-neighbour matching with a delta-e relevance band (exact/close/approximate/loose), full provenance, and that the result already carries rendered palette plus PNG/PDF/ASE/JSON/CSS downloads. It also exposes a critical behavioral constraint about not presenting derived anchor colours as recommendations. This goes well beyond the annotation and materially changes how the agent should use the result.

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 dense but every sentence earns its place: mechanism, use cases, output contents, guardrail, and downstream routing to palette_finalize. It is front-loaded with the core function and contains no filler or redundant restatements of the tool name. Despite its length, it is efficient and structured around decision-relevant information.

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 tool with only 3 parameters, a readOnly annotation, and an output schema, the description is complete. It covers purpose, concrete usage contexts, behavioral guardrails, return output contents, and the correct follow-up action when the agent personalizes the result. Nothing an agent needs to call this tool correctly or interpret its output 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 under the rubric. The description adds value by explaining the delta-e relevance bands, which directly relates the max_delta_e parameter to the qualitative classification of matches, and gives concrete examples for the target_archive parameter (Shakespeare, Japan, Oxfordshire). This is marginal but meaningful enrichment beyond the schema.

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 opens with a specific verb and resource: 'Map any list of hex values into a target archive using CIEDE2000 nearest-neighbour matching.' It clearly distinguishes this from sibling tools like palette_generate or archive_search by naming the exact mechanism and outlining concrete translation scenarios. An agent can immediately tell this is a palette translation tool, not a palette creation or archive exploration tool.

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: translate client paint colours into Shakespeare language, map brand palettes into historical Japanese pigments, or find Oxfordshire equivalents to a French scheme. It also provides a clear exclusion ('Never present the archive anchors... as the colours you are recommending') and an alternative action ('call palette_finalize once with those exact colours') when the agent intends to choose its own final palette. This fully routes the agent between tools.

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