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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely new context: it is computation-only with no upload, charge, account record, or closet inference, and it clarifies unknown colors trigger a clarification request. That supplements the safety profile rather than restating it.

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?

Three dense sentences, front-loaded with the generated artifacts before the prerequisites and side-effect disclaimers. No filler, though the clause-heavy final sentence is densely packed.

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 need no explanation, and the description covers purpose, precondition, and side-effect boundaries well. The main gap is the undocumented "occasion" input, which an agent would have to discover from the schema.

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 0%, so the description must carry the load: it covers palette_ref, purpose (outfit/event/packing), and optional garment colors, but omits the "occasion" parameter entirely and does not explain that colors may be given as hex or name. Partial compensation for a 4-parameter tool.

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 (Generate) and concrete resources (labeled downloadable SVG board and matching 12-color PNG), plus the inputs that drive them. It is distinguishable from the retrieval-style sibling get_palette_board and from select_palette/compare_colors, though it never names a sibling outright.

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?

"Requires the user's chosen palette; unknown colors request clarification" gives a precondition and a fallback behavior, which is real usage guidance. However, it never says when to pick this tool over select_palette or get_palette_board, so the routing is only implied.

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