Opentoonz Render Batch

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 per-scene failure isolation ('One scene failing does not stop the rest'), per-scene OK/FAILED reporting, and output naming, but it leaves side effects such as overwrite behavior, output location, and auth requirements unstated.

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 definition is three short paragraphs with the core purpose front-loaded and no obvious filler. The parameter guidelines are dense but readable, though the final sentence about the structured payload slightly duplicates the preceding reply-format statement.

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?

For a 9-parameter batch tool with no annotations and no output schema, the description covers core behavior, parameter applicability, output reporting, and failure isolation. It is not fully complete because out_name/workspace remain undocumented and sibling routing is left implicit.

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 supply parameter meaning. It does this well for most parameters: scenes defaults to every scene, kind accepts frames/video/gif, fps applies to video/gif, start/end are inclusive and frames-only, and crf/scale are video-only. However, out_name and workspace are not explained at all.

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 several scenes in one call, reporting each scene's own result.' The word 'several' and 'batch' distinguish it from single-scene render siblings such as opentoonz_render_frame or opentoonz_render_video, but no sibling is named explicitly.

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?

Usage is implied for multi-scene batch rendering, but the description does not say when to choose this over single-scene render tools or over opentoonz_render_video/opentoonz_render_gif. It explains parameter applicability once the tool is selected, not when to select it.

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