Color Matching: regenerate variants

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the output behavior – 'Result files are saved to disk and their paths returned' – and by implying credit consumption via estimate_only, though it does not discuss failure modes or overwrite semantics (that detail lives in the schema).

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?

Four tight sentences, front-loaded with the pipeline position and the key input relationship, with no filler. Slightly terse on the remaining ten parameters, but nothing is redundant or padded.

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 12-parameter, non-idempotent, open-world job tool with no output schema, the description covers the essentials: what it produces, where files land, and how it chains from the grid step. The safety/execution annotations plus the schema's per-parameter detail fill the remaining slots, so nothing critical is missing.

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 baseline is 3. The description still adds meaning: it clarifies that 'image = the ORIGINAL design used for the grid' (not the grid image), establishes grid_task_id as the preferred alternative to grid_image_url, and ties bg_only back to the grid run's value. That is genuine value beyond the per-parameter text.

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 resource – regenerate full-size images for chosen swatch-grid cells – and positions itself precisely as 'Color Matching Auto step 2' relative to the grid step. It names the sibling tool (td_color_matching_swatch_grid) as the source of grid_task_id, so an agent can place it in the pipeline without opening either schema.

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: getting clean, full-size versions of the swatch-grid variants you liked' line gives clear when-to-use context and anchors it after the grid run. It does not, however, state any when-not-to-use conditions or what to do if the grid was never run, so it stops short of full routing guidance.

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