render_batch

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

The description adds useful behavioral context beyond the annotations: it states that the call blocks until done and is slow, and that it returns the write result per job. This goes beyond the destructiveHint=true annotation by explaining the blocking and per-job result nature. However, it doesn't elaborate on what destructive means (e.g., file overwriting) or behavior on partial failure, so it adds some but not rich context.

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 bilingual, providing the same information in Chinese and English. It front-loads the core purpose and then explains the jobs parameter and blocking behavior. While the duplication could be redundant for a single-language audience, it serves international users. The text is concise and well-structured, earning a solid score.

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 batch tool with a nested object parameter and no output schema, the description covers the basic structure, return type, and blocking behavior. However, it omits important details such as error handling (what happens if one job fails), prerequisites (e.g., cameras and paths must exist), and whether the operation is atomic. These gaps are significant for a batch operation, so the description is adequate but incomplete.

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?

The schema already documents that jobs is an array of objects with camera, path, and frame, and the description repeats this information without adding further detail such as data types or required fields per item. With schema description coverage at 100%, the baseline is 3, and the description provides no additional semantic value beyond the schema.

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 clearly states it queues multiple camera/path/frame combinations in one call, which is specific and distinct from single-render tools. It uses the verb 'queue' and specifies the resource types, making the purpose unambiguous. However, it doesn't explicitly name sibling tools like render_still or render_frames to differentiate, so it loses a point for lack of explicit distinction.

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_still, render_frames, or render_animation. The description only explains what it does, not the conditions that would make batching preferable. An agent would have to infer that this is for multiple independent renders; no explicit 'use this when' or 'instead of' is provided.

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