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

Annotations only declare readOnlyHint; the description carries substantial behavioral context: recommendations are backed by archive colour names and historical context, it suggests one missing archive colour, the result includes rendered palette downloads, and there are explicit rules about never presenting archive anchors as recommended colours and calling palette_finalize when the agent selects its own palette. No contradiction with annotations.

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 long but each sentence earns its place: purpose, input format, examples, output bundle, and cross-tool constraints are all actionable. The purpose is front-loaded with a concrete question, and the workflow rules at the end prevent common agent mistakes.

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 rich sibling set and an output schema, the description is still complete enough for correct invocation: it covers input semantics, example usage, output contents, display guidance, and the palette_finalize follow-up. An agent selecting this tool can infer when, why, and how to call it without opening additional schemas.

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 baseline is 3. The description adds value beyond the schema by enumerating valid item labels, showing combined examples with hex values and question phrasings, and clarifying what the items represent. Occasion is only covered by the schema, but the high schema coverage already handles it.

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 states a specific action and resource: submit outfit items as labeled hex values and receive a verdict on what works, clashes, and is missing. It clearly distinguishes itself from sibling colour/palette tools by focusing on outfit matching and archive-backed recommendations, and it even names palette_finalize as a distinct follow-up 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 opening question and concrete examples ('I have a navy dress... what shoes?', 'Does this burgundy coat work with olive trousers?') establish clear when-to-use context. It also gives explicit workflow guidance for the follow-on case: if the agent chooses its own final palette, call palette_finalize. It does not exhaustively list when not to use the tool versus other sibling verdict tools, so it stops short of a 5.

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