Create layer stack (N-layer compositor)

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

The description details the internal node construction (Select, Level, Composite TOPs), exposes a live control strip with per-layer parameters, and specifies return values including node paths, errors, warnings, and a preview image. This adds substantial value beyond the annotations, which only indicate non-read-only and non-destructive behavior.

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 detailed but efficiently structured, starting with the core purpose and then layering behavioral details. Each sentence adds value, though slightly lengthy; could be marginally tighter but remains clear.

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?

Given the complexity (5 parameters, nested arrays, no output schema), the description covers all necessary aspects: how layers are composed, control exposure, return format. It leaves no obvious gaps for an agent to make errors.

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%, but the description enriches understanding by explaining how parameters fit into the compositing logic (e.g., bottom-up stacking, test sources when omitted). It connects parameter roles to the overall behavior beyond their individual 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 title and description clearly state 'Build a VJ-style N-layer compositor' with specific verbs and resources (source TOPs, blend modes, opacity). It distinguishes from siblings like create_layer_mixer by detailing the per-layer composite structure and control strip.

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 usage for VJ-style compositing but does not explicitly state when to use this tool over alternatives like create_layer_mixer. It lacks guidance on when not to use it or prerequisites.

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