render_animation

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the filepath-prefix-plus-frame-suffix naming convention and that it returns a confirmation dict, but it omits whether the operation is long-running/blocking, that it depends on scene frame-range and render settings, and that it produces persistent side effects on disk.

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 Args/Returns structure is clean and front-loaded with the core action, and every line is short. It is slightly formulaic but contains no filler sentences.

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 the description need not detail the return structure, and it covers both parameters. But for a filesystem-writing render tool with zero annotation coverage, it should at minimum state prerequisites and side effects; without those it is only minimally adequate.

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%, so the description must compensate, and it largely does: it explains that filepath is a prefix with a frame-number suffix appended per frame, which is genuine meaning beyond the schema. The format argument merely re-lists the enum values already enforced by the schema, so it adds little there.

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 and resource ('Render the animation sequence') plus the output artifact ('image files'), so the agent knows it is an animation render rather than a single-frame render. It does not, however, name or contrast itself with the sibling render_image, leaving the sequence-vs-single distinction implicit.

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?

There is no when-to-use guidance: no mention of prerequisites (an active camera, a configured frame range/output format), no note that this writes persistent files to disk, and no routing to alternatives such as render_image or set_frame_range. The only 'guidance' is the bare statement of purpose.

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