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

Adds substantial behavior beyond readOnlyHint: deterministic and no LLM cost; result includes rendered palette and downloadable assets; warns not to present archive anchors as recommended colours; requires palette_finalize if the agent chooses its own palette. This gives the agent clear expectations about side effects, output content, and downstream workflow.

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 dense but every sentence earns its place: core purpose, scoring dimensions, output, usage gate, cost profile, return contents, and critical workflow warnings. It is well front-loaded and structured so the most important usage information comes first.

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 and annotations declare readOnlyHint, the description covers what the tool returns, how to present results, what to avoid, and how to proceed afterward. Nothing essential is missing for an agent to invoke and use the tool correctly.

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 schema already documents the four parameters. The description does not add deeper parameter-level guidance (e.g., format expectations for palette entries or how market/medium affect results), but the baseline of 3 is appropriate given full schema coverage.

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 clearly states that this is a 'full palette quality audit' with specific scoring dimensions (accessibility, cultural risk, tonal balance, colour diversity, archive naming strength) and a concrete output (0-100 score, grade, fix list). This distinguishes it from sibling tools like palette_analyse or palette_verdict by defining its exact scope and 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 gives an explicit usage context: 'Enterprise quality gate -- use before shipping any palette.' It also routes to palette_finalize when the agent selects its own final palette. However, it doesn't explicitly state when NOT to use this tool or name alternative audit/analysis tools for lighter checks.

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