blender_render

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

No annotations are provided, so the description carries the full burden. It mentions that directories must exist for output, but does not disclose behavioral traits such as file overwrite policy, whether the tool modifies the Blender scene permanently, performance implications, or error handling. This is a significant gap for a render tool with 11 parameters.

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: a rationale paragraph, a one-sentence purpose, then a clear bulleted list of operations. Each section adds value without redundancy. It is appropriately sized for the tool's complexity and front-loads the key information.

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 (11 params, four operations), the description covers operation selection and parameter usage but lacks completeness on behavioral aspects (e.g., file overwriting, scene interaction, error handling). The presence of an output schema (not shown) may compensate, but as evaluated, the description leaves gaps for safe usage without additional context.

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 already provides 100% coverage with defaults, ranges, and descriptions. The description adds value by grouping parameters per operation (e.g., 'render_preview uses: output_path, resolution_*, ...'), helping agents understand which parameters are relevant for each sub-mode. This organizational insight reduces ambiguity beyond 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 it is a 'Professional rendering system for Blender supporting previews, animations, and custom output formats' and then enumerates four specific render operations (preview, turntable, animation, current frame). This provides a specific verb+resource and distinguishes the tool from sibling tools focused on modeling, scene setup, or export.

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 detailed guidelines on when to use each of the four sub-operations (via the bullet list and parameter associations). However, it does not explicitly compare this tool to sibling tools like blender_export or blender_animation, nor give 'when not to use' advice. The rationale for consolidation is mentioned, providing context.

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