blender_compositor

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

Annotations are all false, providing no safety profile. The description only gives surface-level operations (e.g., 'add a compositor node') without disclosing side effects, required Blender state, or reversibility. It does include the return format for success/message/data, but that's not behavioral context.

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 well-structured with a bullet list, return format section, and example. It is concise and scannable, though the 'Operations' list could be slightly more compact if parameters were documented elsewhere.

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 13 parameters, 4 operations, no schema descriptions, and no annotations, the description falls short. It provides an overview and an example but omits parameter semantics, per-operation prerequisites, and broader Blender context needed to invoke it reliably.

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 0%, and the description does not map any of the 13 parameters to operations. Some parameters are inferable (e.g., from_node/to_node for connect_nodes) but not explicitly documented, leaving users to guess the roles of glow_size, use_sequencer, etc.

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 states the tool handles 'Compositor graph operations for post-processing' and enumerates specific sub-operations (enable, add_node, connect_nodes, glow) with short explanations. While it doesn't explicitly contrast with sibling tools, the compositor focus distinguishes it from other Blender 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?

The description implies usage for post-processing via the opening line and provides a simple example. However, it lacks explicit guidance on when to choose this tool over siblings like blender_render or blender_shaders, and does not explain when to use each sub-operation beyond their brief descriptions.

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