color_set_cdl

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

No annotations are provided, so the description must carry full burden. It only states the operation ('Set') and target, but does not disclose side effects (overwriting existing values), requirements (open timeline, valid item), or reversibility. This is insufficient for a mutating tool.

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?

A single, direct sentence with no superfluous words. Every word adds clarity.

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?

The presence of a detailed schema and output schema reduces the burden, but the tool is part of a complex color-grading context with many sibling tools (color_get_cdl, color_set_lut, cdl_write). The description does not explain prerequisites like the need for an open timeline or how this differs from cdl_write. With no annotations, some behavioral gaps remain.

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 100% with detailed descriptions for all parameters, including the CDL dictionary structure. The description adds no extra parameter-level meaning, so baseline 3 applies.

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 uses a specific verb ('Set') and resource ('ASC CDL values') and identifies the target scope ('on a timeline item's current node'). This clearly distinguishes it from siblings like color_get_cdl (reading) and color_set_lut (different color operation).

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 description implies the context of color grading operations on a timeline item's current node, but does not explicitly mention when to prefer it over alternatives like color_get_cdl or cdl_read. Context is clear but no exclusions provided.

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