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

Annotations only declare readOnlyHint=true. The description adds substantial behavioral context beyond that: the result already carries rendered palette downloads (PNG, PDF, ASE, JSON, CSS) and should be shown to the customer. It also warns never to present archive anchors as recommended colours and specifies the downstream palette_finalize call when needed. This meaningfully discloses output behavior and usage constraints.

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 front-loaded with purpose and outputs, then adds high-value operational guidance. Each sentence earns its place: the finalization instruction and the warning about archive anchors are important for correct agent behavior and are not filler. It is dense but not bloated.

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, return-value details are not mandatory, but the description still covers them and adds important workflow context (show downloads to customer, avoid presenting derived anchor colours as recommendations, call palette_finalize for own selected palette). This is complete for correct invocation and downstream behavior.

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 references the 'stated use case' and two palettes but does not add detail beyond the schema for markets or input formats. It does not need to compensate because the schema already documents every parameter.

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 starts with a specific verb plus resource: 'Deep perceptual, cultural, and commercial comparison between two palettes.' It enumerates concrete outputs (timelessness scores, commercial strength, cultural depth, emotional difference, winner verdict), which clearly distinguishes it from sibling analyse/verdict/generate tools. The title is also reinforced rather than merely restated.

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 states the core use case: comparing two palettes for a stated use case. It provides an explicit alternative branch: if the agent chooses a final palette of its own from the evidence, it should call palette_finalize with those exact colours. It does not explicitly exclude colour_compare or palette_verdict, but the routing to palette_finalize gives clear contextual guidance.

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