blender_render_animation

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that output goes to files; it does not disclose whether rendering blocks, how start/end frames behave when omitted, whether existing files are overwritten, or what the tool returns.

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 a single, front-loaded sentence with no redundant words. It is concise and well-structured, though the brevity limits how much behavioral context it can provide.

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?

Rendering an animation is a non-trivial operation with no annotations and no output schema. The description omits important context such as default frame range behavior, placeholder requirements, file format defaults, and whether the operation blocks until completion. The schema documents parameter names but not the full execution 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 describes all four parameters with 100% coverage, so the baseline is 3. The description adds no extra parameter meaning, but it does not need to because each parameter already has a schema description, including 'Output path (with frame placeholder)'.

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 'Render the animation to files' clearly identifies the verb (render), resource (animation), and output target (files). It distinguishes this from sibling tools like blender_render_image and blender_render_screenshot, though it does not explicitly contrast with blender_render_multi_angle.

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 gives no guidance on when to use this tool versus alternatives like blender_render_image or blender_render_screenshot, and no prerequisites are mentioned. Usage is only implied by the word 'animation' in the tool name and description.

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