Translate Any Palette into a Named Archive

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

The description discloses the algorithm (CIEDE2000 nearest-neighbour) and relevance bands (exact/close/approximate/loose), adding behavioral context beyond the readOnlyHint annotation. It also mentions 'full provenance' and the mapping process, giving the agent a clear picture of the tool's behavior without contradiction.

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 concise, with two short paragraphs that front-load the core action ('Map any list of hex values...') and immediately provide illustrative examples. Every sentence serves a purpose, and there is no redundant 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?

Given the presence of an output schema, the description does not need to detail return values. It covers the algorithm, use cases, and behavioral traits. However, it could briefly mention what 'full provenance' includes, but overall it is sufficiently complete for a translation tool with defined outputs.

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?

The input schema covers all parameters with descriptions, achieving 100% coverage. The description adds some context (e.g., delta-e relevance bands) but does not significantly enhance understanding beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool's purpose: mapping hex values to named archives using CIEDE2000 nearest-neighbour matching. It provides specific examples that distinguish it from sibling palette tools, such as palette_audit or palette_compare, by focusing on translation into named archives like 'Shakespeare' or 'Japan'.

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 concrete use cases (e.g., translating client paint colours into Shakespeare language) that implicitly guide when to use this tool. However, it lacks explicit guidance on when not to use it or how it differs from siblings like palette_compare, leaving some ambiguity for the agent.

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