Create a basic node setup linking render layers to a composite node and viewer for rendering.
Template: Create Render Layers -> Composite + Viewer setup.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0+hardened.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It says it creates nodes, but does not disclose whether it modifies an existing compositor tree, whether it clears prior nodes, whether it enables the compositor, or whether the setup is idempotent.
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 very short with no filler, and the arrow notation compactly conveys the node relationship. It could be slightly clearer grammatically, but it is appropriately concise for a zero-parameter convenience tool.
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 zero-parameter operation, the high-level outcome is stated and an output schema exists, which reduces the need to explain return values. However, the description omits important behavioral context such as whether existing node trees are replaced and whether compositor enabling is handled, so an agent may be surprised by side effects.
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?
The tool has zero parameters and the schema covers 100% of them, so there is nothing for the description to add. The baseline of 4 applies because no parameter documentation is needed.
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 setup action: creating Render Layers, Composite, and Viewer nodes in a basic compositing template. It is clear enough to distinguish this macro-style tool from individual compositor node tools like create_comp_node, though it does not explicitly name a sibling or contrast its scope.
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?
No guidance is given about when to use this tool versus manually building a node tree with create_comp_node and connect_comp_nodes, or versus using enable_compositor first. The description implies a convenience template but leaves usage conditions entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.