Color Matching: suggest colours

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

Annotations already declare it is not read-only, not idempotent, and open-world. The description adds useful side-effect context beyond annotations: it returns JSON plus mapping sets, saves result files to disk, and returns their paths. It does not mention credit use or waiting behavior, but those are partially covered by schema parameters.

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 front-loaded with the tool identity and core action, and its four sentences are mostly efficient. There is slight redundancy: 'for a market and palette type' appears in the first sentence and again in the 'Best for' sentence, but the structure remains clear and navigable.

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 no output schema, the description does explain the return shape (JSON plus mapping sets, saved file paths), which is essential. The remaining 12-parameter complexity is handled by the schema's 100% description coverage, so the description is sufficient for a caller, though it could briefly note credit estimation or the async/wait behavior.

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 all 12 parameters in detail. The description only reinforces that the palette comes from extract_task_id or colors and mentions market and palette type, adding little beyond the schema's own descriptions. Baseline 3 is appropriate.

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 verb and resource: five palette suggestions for a market and palette type, sourced from an extracted palette. It distinguishes itself from upstream extraction (extract_task_id or colors) and downstream replacement (td_color_matching_replace), and 'trend-aware palette ideas for a target market and palette type' differentiates it from reference-matching and swatch-grid siblings.

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 provides clear context with 'Best for: getting trend-aware palette ideas for a target market and palette type' and identifies which inputs to source from. However, it does not explicitly state when not to use it or name alternative tools like td_color_matching_regenerate or td_color_matching_match_reference, so it stops short of the 5-level alternative routing.

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