blender_workflow

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

With all annotations false, the description carries the burden. It discloses sequential execution, optional variable passing, and conditional step execution via 'if_result'. It does not mention potential side effects on Blender state, but as a workflow orchestrator, effects depend on the underlying operations.

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 sections (OPERATIONS, STEP FORMAT, VARIABLE REFERENCES) and each sentence provides necessary information. While somewhat lengthy, no unnecessary fluff is present.

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 complex orchestration tool, the description covers operations, step syntax, and variable references, and the output schema likely handles return values. It lacks explicit error behavior details, but stop_on_error is in the schema. Given the tool's complexity, it is reasonably complete.

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 input schema covers all parameters with basic descriptions (100% coverage), but the description adds substantial meaning by detailing the step format ('tool', 'operation', 'as', 'if_result') and variable reference syntax ($varname and ${varname.field}), which are not obvious 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 opens with 'Execute multiple Blender operations in a single call (macro/batch)', clearly stating the tool's purpose. It lists specific operations (list_templates, get_template, execute) and distinguishes from siblings by emphasizing multi-step workflow execution.

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?

It provides clear context: 'This tool enables complex workflows without multiple round-trips to the MCP server', implying use for multi-operation workflows. However, it does not explicitly name alternatives or state when not to use it, leaving some ambiguity versus tools like blender_batch or script_execute.

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