Color Transfer

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

Annotations already declare openWorldHint, non-read-only, non-idempotent and non-destructive. The description usefully adds the output behavior — files written to disk with paths returned — but says nothing about credential/plan requirements, credit consumption, or the wait/task_id async model that a mutation tool arguably should surface.

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 compact sentences with the core action and the payoff (disk paths) front-loaded. The 'Best for:' sentence partly restates the opening line's mechanism before adding the new examples, which is mild redundancy but not waste.

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?

For a tool with no output schema, the description covers the destination and form of the result (files on disk, paths returned), which is the key return-value fact. Async/task_id handling, credit estimation and review_settings prompting are all covered by the schema, so the remaining gaps are small.

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 eight parameters in detail, including defaults and constraints. The description adds no parameter-level meaning beyond that baseline, which is the expected 3 when the schema carries the full load.

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 transform ('recolour the source design with the palette of a second image') and adds that structure/composition are preserved, which implicitly separates it from td_style_transfer. It stops short of naming sibling tools such as td_style_transfer or td_color_matching_match_reference, so differentiation is inferred rather than explicit.

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?

The 'Best for:' clause gives a clear use case with concrete examples (seasonal trend colours, buyer brand colours) on an existing design. There is no statement of when NOT to use it or which alternative to pick for a related goal (e.g. style transfer vs palette transfer), so usage is contextual but not routing.

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