Render a bounded PNG preview sequence from the scene camera, saving a checkpoint and restoring settings to protect the current scene.
Render a bounded PNG sequence using scene camera; save checkpoint and restore settings.
| Name | Required | Description | Default |
|---|---|---|---|
| step | No | ||
| width | No | ||
| height | No | ||
| frame_end | No | ||
| max_frames | No | ||
| frame_start | No | ||
| operation_id | No | ||
| allow_cpu_fallback | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish that this is a non-read-only, non-destructive, non-idempotent operation. The description adds useful behavioral context by stating that it saves a checkpoint and restores settings, which signals a temporary scene mutation, but it does not explain where files are written, how the checkpoint is used, or how CPU fallback affects behavior.
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 front-loaded sentence with no filler. It is appropriately concise, though for an eight-parameter render operation it is terse enough that important details are omitted rather than merely compressed.
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, and annotations cover basic safety hints. However, for a render tool with eight undocumented parameters and checkpoint/restore behavior, the description is too incomplete to guide correct invocation; it omits parameter meanings, output location, and CPU fallback implications.
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 description names no parameters, while the schema has eight parameters with 0% description coverage. Terms like 'bounded PNG sequence' hint at frame bounds and image dimensions but do not explain operation_id, allow_cpu_fallback, step, max_frames, or the frame range parameters.
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 and resource: render a bounded PNG sequence using the scene camera. It distinguishes the operation from a generic capture by specifying a bounded rendered sequence, but it does not explicitly differentiate itself from close siblings such as qa_render_multiview or qa_capture_viewport.
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?
The description gives no explicit guidance on when to use this tool versus alternatives. It does not mention when qa_render_preview is preferable to qa_render_multiview, qa_capture_viewport, or other preview/render tools, nor does it state any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.