blender_render_animation

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

With no annotations, the description carries the behavioral burden, and it does disclose that 'headless' spawns a separate background Blender process while 'bridge' targets the live session. However, it says nothing about whether rendering is blocking or returns a job handle, nor about timeouts or failure modes for a long-running render.

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?

Two sentences, front-loaded with the action and followed by the mode-selection detail. Every clause carries information; nothing is redundant.

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?

An output schema exists, so return values need not be explained, but the presence of sibling job tools (blender_job_status, blender_job_list, blender_job_cancel) suggests renders may be asynchronous, and the description never says whether this call blocks or hands back a job id. That is a meaningful omission for a 7-parameter render tool.

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% for 7 parameters, so the description must compensate. It names output path, frame range, engine, transport, and the role of blend_file, but leaves factory_startup and the frame_start/frame_end split undocumented, so it only partially fills the gap.

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?

States a specific verb+resource ('Render an animation') and is immediately distinguishable from the sibling blender_render_still. The follow-on sentence clarifies the two operational modes without muddying the core purpose.

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?

Explicitly routes between transport='bridge' (live add-on session) and transport='headless' with a blend_file (separate background process), which is the key decision an agent must make. It does not state when to prefer this tool over blender_render_still, though that distinction is self-evident from the names.

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