batch_render

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'Render from multiple cameras sequentially,' but doesn't mention that it writes files to output_dir, may take a long time, overwrites existing files, or blocks. An agent cannot anticipate side effects or system impact from this description alone.

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 a single sentence with no fluff, which is concise, but it is far too sparse for a tool with six parameters. It front-loads the basic action but omits necessary detail, making it under-specified rather than appropriately concise. The structure is not aligned with the tool's complexity.

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?

Given the tool's complexity (6 params, 0% schema coverage), the description is severely incomplete. It lacks instructions on camera name format, output directory requirements, accepted formats, sample ranges, and resolution constraints. Even though an output schema exists, the input parameters are undocumented, leaving an agent unable to construct valid calls. This is far below the minimum viable.

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 explain parameters, but it doesn't mention a single parameter. camera_names, output_dir, format, samples, and resolution dimensions remain completely unexplained. The description adds zero value beyond the raw schema, which itself lacks descriptions. This is a critical failure.

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 clear verb ('Render') and resource ('multiple cameras') and adds the sequential aspect, which distinguishes it from single-render tools. However, it doesn't explicitly differentiate from sibling tools like render_image or render_turntable beyond that, so it's clear but not fully discriminating. A 4 is appropriate given the moderate specificity.

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 guidance on when to use this tool versus alternatives such as render_image, render_turntable, or batch_export. The description doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage. This is a significant gap for a tool with multiple siblings that could overlap.

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