setup_basic_composite

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

With no annotations, the description must disclose behavioral traits, but it only states the nodes to be created. It does not mention side effects like clearing existing node trees, whether it overwrites current compositing setups, or any dependencies (e.g., render layer existence). This lack of detail makes potential impacts unpredictable.

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 a single, terse line that is front-loaded and free of filler. It conveys the core idea efficiently, but it is slightly under-specified, lacking behavioral context. This brevity is acceptable for a template description, though it sacrifices completeness.

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 tool's role in compositing setup and the extensive list of sibling tools, the description is incomplete. It does not provide enough context about the resulting node tree, potential side effects, or any setup steps needed before invocation. The presence of an output schema is not disclosed, so the agent cannot infer return value structure.

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, so the schema is trivially complete. The description does not need to explain parameter behavior since there are none. Baseline for zero parameters is 4, and the description neither adds nor detracts from this.

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 clearly indicates the tool creates a composite setup with render layers, a composite node, and a viewer node. While it is phrased as a template rather than a full sentence, it effectively conveys the specific resource and action. It does not explicitly differentiate from sibling compositing tools, but the focus on a basic setup is implicit.

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 provides no guidance on when to use this tool versus alternative compositing tools or manual setup. It does not mention prerequisites, such as whether the compositor must be enabled, nor does it indicate when this template is preferred over creating nodes individually.

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