render_animation

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

Annotations already mark this as destructive, and the description adds meaningful behavioral context beyond that: the call blocks until completion and full sequences can take minutes. This is useful operational information and does not contradict the annotations.

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 English portion is tight and front-loaded: action, output format, then performance warning. The bilingual duplication adds length but appears intentional; no filler or irrelevant detail 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?

The description covers core behavior, output granularity, and blocking duration, which is adequate for basic invocation. However, it does not mention overwrite behavior despite the destructive hint, nor does it clarify when to use render_animation versus render_still/render_frames/render_batch. With no output schema, a bit more guidance would help.

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 documents all three parameters at 100% coverage, so the baseline is 3. The description reinforces the notion of a sub-range and per-frame output but does not add new parameter-specific semantics beyond the schema.

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 states a specific verb and resource: "Render the whole animation range or a sub-range, one file per frame." It clearly names the operation and output granularity, though it does not explicitly distinguish itself from siblings like render_frames or render_batch.

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?

No explicit when-to-use versus alternatives such as render_still, render_frames, or render_batch is provided. The warning that full-sequence rendering is slow and blocks gives implicit context for choosing sub-ranges, but it never states when this tool should be preferred over others.

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