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

Description adds context beyond annotations: 'Computation only; no upload, charge, account record or closet inference' reinforces the readOnly/non-destructive hints, and the clarification-on-unknown-colors behavior is a genuine operational trait not visible in schema or annotations. It doesn't cover determinism/idempotency (which annotations supply) or anything about output size, but the added behavioral detail is solid.

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?

Two dense sentences: the first leads with what is produced, the second with prerequisites and safety. No filler, though the trailing 'no upload, charge, account record or closet inference' list is slightly padded and would read better as a short clause.

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?

An output schema exists, so return values needn't be described, and annotations cover the safety profile. Still, for a 5-parameter tool with low schema coverage, the description leaves palette_ref and occasion unexplained and doesn't state how many colors are expected versus optional.

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 only 20% (analytics_opt_out is the lone documented param), so the description must compensate. It loosely covers palette (palette_ref), purpose (outfit/event/packing), and colors ('optional supplied garment colors'), but says nothing about occasion, the hex-vs-name color form, the 12-item cap, or the palette_ref token format.

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 verb and output artifacts: 'Generate a labeled downloadable SVG board and matching 12-color PNG' from a user-confirmed palette and a purpose. It's clearly a creation tool, implicitly distinct from get_palette_board, but it never names a sibling or explicitly contrasts itself with the retrieval/selection 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?

Gives one real prerequisite ('Requires the user's chosen palette; unknown colors request clarification'), which implies it follows select_palette. However, it never explicitly says when to use this vs get_palette_board or which purpose value to pick, and offers no exclusions or alternatives.

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