blender_workflow

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

With no annotations provided, the description carries full burden. It details sequential execution, optional variable passing, step dependencies (if_result), and stop_on_error behavior. It lacks specifics on error handling beyond stopping, but overall provides significant 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 clear sections (overview, operations, step format, variable references) and front-loaded purpose. It is slightly lengthy but each sentence adds value; could be more concise without losing clarity.

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 complexity (6 parameters, 3 operations, conditional logic), the description is quite complete. It explains step sequencing, variable references, and operation behavior. It does not provide examples or clarify return values, but an output schema exists. Adequate for the complexity.

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 description adds substantial meaning beyond the 100% schema-covered parameters. It explains step format, variable reference syntax, operation roles (e.g., template usage), and conditional execution, which are not evident from the schema alone.

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's purpose: 'Execute multiple Blender operations in a single call (macro/batch).' It lists operations (list_templates, get_template, execute) and differentiates from single-operation siblings by enabling complex workflows without multiple round-trips.

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 multi-step workflows needing sequential execution and variable passing, avoiding round-trips. However, it does not explicitly exclude cases where single-operation tools are preferred or compare with the sibling 'agentic_blender_workflow'.

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