agentic_blender_workflow

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

No annotations provided, so the description carries full burden. It discloses the iterative, autonomous nature and max_steps limit, but omits potential side effects (e.g., scene modifications) or what 'capability probes' entail.

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?

Three sentences, each adding essential information: technology, process, and constraints. No redundancy; front-loaded with the core purpose.

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 presence of an output schema and full parameter descriptions, the tool is well-covered. However, it could be improved by clarifying its relationship to similar workflow tools like 'blender_workflow' and 'intelligent_3d_processing'.

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?

Input schema has 100% description coverage for parameters. The description adds context by explaining the workflow_prompt as a natural language goal and highlighting the tool's autonomous probing behavior, which enriches the schema definitions.

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 executes 'autonomous multi-step Blender workflows' via FastMCP sampling. It differentiates from siblings like 'blender_workflow' by emphasizing autonomy and looping behavior.

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 explains when to invoke the tool: for complex goals requiring step-by-step LLM planning. It implicitly excludes simpler operations but lacks explicit 'when not to use' or alternative tools like 'intelligent_3d_processing'.

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