add_scene_color_layers

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

With no annotations, the description carries the behavioral burden and does well: it states that layers are added on a new top track, how layers are named, how same-source clips are grouped, that repeated sources get identical names and Lumetri values, and which item types are skipped. It still leaves some mutation details unstated, such as idempotency or what happens if layers already exist.

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 dense but front-loaded and every sentence contributes required information: the core action, grouping rules, skip rules, and optional Lumetri parameters.

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 complex timeline mutation tool with no annotations and no output schema, the description explains the key grouping and side-effect logic well. It does not explain return values or how reruns interact with existing layers, which keeps it from being fully complete.

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 five parameters. The description adds some meaning by distinguishing basic values for all scenes versus perSource values by source file name, but it does not add much beyond the schema descriptions.

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 operation: creating one adjustment layer with Lumetri Color per SOURCE for scene-level grading. It also defines the grouping and naming behavior, which clearly separates it from generic adjustment-layer tools.

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 useful workflow context, including calling sync_color_layers after grading one layer to keep repeated sources identical, but it does not explicitly say when to choose this tool over siblings like build_scene_adjustment_layers, add_color_layer, or add_adjustment_layer.

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