Opentoonz Render Gif

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

No annotations are provided, so the description carries the full behavioral burden. It discloses meaningful traits: the palette cap (2–256), downscaling via max_width, no audio support, and lossy resolution trade-offs. It does not say where the output file is written or whether existing files are overwritten, which is the remaining gap for a write-to-disk tool.

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?

Three sentences, front-loaded with the core action, then parameter guidance, then sibling routing. Every clause carries information; no filler.

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?

With no annotations, no output schema, and 6 parameters at 0% schema coverage, the description would need to cover more ground. It handles the rendering parameters well but leaves workspace/scene identity and output naming/location unexplained.

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 does explain fps, max_width, and colors with usable ranges and intent. However, scene, workspace, and out_name (default 'reel', i.e. where the artifact lands) are entirely undocumented in both schema and description.

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 a scene to a looping GIF') and immediately positions it against the sibling opentoonz_render_video by naming the distinguishing axis (audio/full resolution). An agent can select it without opening the schema.

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?

Explicitly routes the alternative case: 'use that [render_video] for anything with audio or that must stay full resolution,' which is a concrete when-not condition. It also clarifies that frames come from the same tcomposer pass, removing a workflow ambiguity.

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