render_animation_sequence

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

No annotations exist, so description must carry full burden. It fails to mention any behavioral traits: output format, file creation, side effects on scene, or permissions needed. Minimal transparency.

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?

Extremely concise at three words, with no fluff. Every word earns its place. Could be slightly improved with structure (e.g., front-loading verb), but acceptable.

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?

Despite an output schema being present, the description fails to mention what the tool returns. With sibling tools in animation/rendering and a vague parameter, the description is insufficient for an agent to use correctly.

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 has 0% coverage for parameter 'kwargs', which is a required catch-all with no type or description. The description adds no meaning to the parameter, leaving the agent completely uninformed about what to pass.

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?

Description states a verb ('Render') and resource ('animation sequence'), clearly indicating the tool's core action. However, it does not distinguish from sibling tool 'render_preview' or specify scope (e.g., which scene/range). The purpose is understandable but lacks specificity.

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 guidance on when to use this tool vs alternatives like 'configure_render_settings' or 'set_timeline_range'. No prerequisites, exclusions, or context provided. The description gives no usage scenario.

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