render_animation

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

With no annotations provided, the description carries the disclosure burden. It does reveal that the operation is long-running, which is a significant behavioral trait. However, it omits other details like potential output files, whether it blocks, or if it depends on render settings, leaving gaps in what an agent should expect.

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 two succinct sentences with no wasted words. The core action is front-loaded, and the behavioral note follows efficiently. It is appropriately sized for a tool with no inputs.

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 the essential action and warns of duration, but it omits context like reliance on current render settings, expected output location, or error behavior. Since an output schema exists, return format is not required, but for a render tool the description is minimal and leaves some operational ambiguity.

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?

There are no parameters in the schema, so the description does not need to explain parameter meaning. The empty schema obviates the need for parametric documentation; the baseline of 4 applies, and the description adds no irrelevant parameter info.

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 (Render) and a clear resource (full animation frame range), making the tool's purpose distinct from siblings like render_image and render_viewport. However, it does not explicitly name alternatives, relying on the sibling names to suggest the difference.

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 implies when to use this tool—for full animation rendering—and the note about long-running operation suggests not for quick previews. Yet it does not explicitly contrast with render_image or render_viewport, nor does it state prerequisites or when not to use it.

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