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

Beyond the readOnlyHint annotation, the description discloses that the result carries a rendered palette and downloadable assets, tells the agent to show them to the customer, warns against presenting archive anchors as recommended colors, and defines the palette_finalize handoff for agent-chosen palettes. This is substantial behavioral context and is consistent with the read-only annotation.

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?

Every sentence carries distinct information: the comparison scope, the concrete outputs and presentation requirement, a safety guardrail about derived anchors, and the follow-up tool call. The description is front-loaded with the core purpose and contains no filler.

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 an output schema and read-only annotation, the description is complete: it defines the comparison, names the delivered assets, states customer-presentation behavior, and prescribes the next action if the agent chooses its own palette. No critical calling detail 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 adds only indirect parameter nuance by linking the comparison to 'the stated use case' and does not explain hex formats or markets structure, but the schema already documents those details.

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 names a specific operation — a deep perceptual, cultural, and commercial comparison of two palettes — and enumerates concrete outputs: timelessness scores, commercial strength, cultural depth, emotional difference, and a winner verdict. This makes it clearly distinct from sibling tools like colour_compare or palette_verdict.

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 makes clear the tool is for comparing exactly two palettes and evaluating them for a stated use case, which strongly implies when it should be called. It does not explicitly name alternatives or state when not to use it, but it does provide valuable workflow guidance by instructing the agent to call palette_finalize if it selects its own final palette.

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