Project Render Batch

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. 'One worker process' reveals a useful execution trait, but the description omits critical details such as whether rendering writes files, permissions/auth requirements, failure handling, and whether mode affects output.

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 single sentence is front-loaded and waste-free, but its extreme brevity leaves the tool underspecified for a batch rendering operation. Conciseness is achieved at the cost of necessary detail.

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 return values need not be described. However, with no annotations, 0% schema description coverage, and three parameters including a mode enum, the description is not complete enough for an agent to confidently invoke this batch render tool.

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%, and the description does not explain any of the three parameters. It vaguely references 'scenes' but gives no meaning for project_id, scene_ids, or the preview/final mode enum, leaving the agent to infer behavior from parameter names alone.

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'), resource ('scenes'), and batch scope ('many scenes in one worker process'). This distinguishes it from per-scene render tools like scene_render_preview and scene_render_final by explicitly indicating batch behavior, though it does not name those siblings.

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 scene_render_preview, scene_render_final, project_build, or project_stitch. The batch wording implies usage for many scenes, but no alternatives or exclusions are stated.

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