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

Annotations carry readOnlyHint=true, and the description is consistent with that while adding substantial behavioral context: the result contains rendered palette plus PNG/PDF/ASE/JSON/CSS downloads, archive anchors must not be presented as recommended colours, and palette_finalize must be called if the agent chooses its own final palette. No 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?

Longer than average, but every sentence earns its place: compound nature, deliverables, replacement relationships, use condition, exclusion, download artifacts, and an important anti-hallucination warning are all front-loaded and dense. 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?

Given the tool's high complexity, seven parameters, many siblings, and an output schema that covers return structure, the description is complete: it covers when, why, what to show, what to avoid, and what follow-up call to make. Nothing essential 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 coverage is 100%, so the schema fully documents concept, medium, avoid, n_colours, and the include_* flags; the description adds little parameter-level meaning. The mention of 'audience' is slightly ambiguous because no audience parameter exists, but this does not seriously undermine the schema-documented parameters.

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?

States a specific compound action—submit a concept/medium/audience/constraints and receive a complete design package—and names the exact single-purpose tools it replaces (query_conceptual, palette_from_concept, colour_story, match_paint_system, accessibility_check, get_colour_metrics), making it unmistakable versus the sibling tools.

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?

Explicitly says when to use it: when a complete, deployable colour direction is needed in a single call, and when not: not for iterative refinement, for which individual tools should be used. It also directs the agent to call palette_finalize if it picks its own final palette from the evidence.

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