Render an OpenToonz scene

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully states that the destination must be new and inside the configured workspace, and that no arbitrary shell commands are exposed, which adds security-related context. However, it omits important behavior such as overwrite handling beyond 'new', permission requirements, failure modes, and what the render produces.

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?

Two tight sentences with no wasted words. The core action is front-loaded, and the safety constraint follows immediately.

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 rendering tool with no annotations and no output schema, the description is too thin. It should explain frame-range controls, timeout behavior, and output expectations, none of which are covered.

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% across 9 parameters, so the description must compensate. It only clarifies that outputPath must be new and inside the workspace; it says nothing about scenePath, frame, frameStart, frameEnd, step, shrink, threads, or timeoutMs, leaving most parameters semantically undocumented.

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 an OpenToonz scene to an image sequence or output file using tcomposer. It is clear what the tool does, but it does not explicitly differentiate its purpose from the sibling render_preview tool.

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 explicit guidance on when to use this tool versus render_preview or the other sibling tools. The distinction between a full render and a preview is implied by the tool name only, leaving the agent to infer the appropriate context.

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