Create layer mixer

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

Annotations are consistent (readOnlyHint=false, destructiveHint=false, openWorldHint=true). Description adds behavioral details: creates new nodes, uses Select TOPs for input flexibility, outputs a Null, returns container paths and preview image. No contradiction.

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?

One paragraph of 5-6 sentences, front-loaded with core purpose, then explains modes, source behavior, output, and return. No redundant sentences, every sentence adds information.

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?

Covers inputs, blend modes, demo sources, output node, and return details (summary, JSON block with paths, errors, preview). Lacks explicit error handling or limitations, but sufficient for a create tool with 4 optional params.

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 covers all 4 parameters with descriptions. Description adds value by explaining demo source creation for inputs and the effect of blend modes, and the expose_controls behavior. Adds contextual meaning beyond schema.

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?

Clearly states the tool builds a VJ-style layer mixer combining source TOPs, with specific verb 'build' and resource 'layer mixer'. Differentiates by describing two modes (crossfade vs other blend modes) and mentions creating a baseCOMP under parent_path.

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?

Describes when to use: for VJ-style mixing, with crossfade for classic two-deck and other modes for compositing. Explains demo source creation with fewer than two inputs. Lacks explicit exclusions or alternative sibling tools, but provides sufficient context.

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