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

Beyond readOnlyHint=true, the description discloses material behaviors: deterministic execution ('Deterministic. No LLM cost.'), and that the result payload already carries the rendered palette with PNG, PDF, ASE, JSON and CSS downloads. It also surfaces the archive-anchor misuse pitfall, which materially changes how an agent should present results.

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?

Roughly five sentences, each carrying operational weight: scope, output contents, determinism, embedded downloads, and the finalize routing. The description is front-loaded with the core promise before the guardrails, and no sentence is filler or redundant with the schema.

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?

With an output schema present and 100% parameter coverage, the description covers everything else an agent needs: what the return value contains, the attached download payload, the explicit follow-up tool condition, and a misuse guardrail. Nothing material is missing for a 5-parameter tool with a single required argument.

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 of 3 applies even though the description adds no parameter-level detail. The only tangential overlap is 'those exact colours' loosely echoing the palette parameter, which the schema already documents as hex values; the description neither contradicts nor enriches the schema.

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 opens with a precise scope statement, 'Complete brand colour system in one call,' and enumerates the concrete contents (colour roles with archive names, light/dark mode maps, typography, usage rules, design tokens, citation cards). This clearly identifies the resource and differentiates it from the many specialized siblings like colour_card, palette_generate, and brand_guideline_pdf which each cover only part of this deliverable.

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?

It explicitly routes a follow-up action: 'call palette_finalize once with those exact colours' when the agent selects its own final palette, naming the alternative tool and the condition that selects it. It also instructs the agent to show the embedded downloads to the customer and states a hard when-not rule about presenting archive anchors as recommendations.

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