render_images

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

Annotations already declare this is a non-readonly, non-destructive, closed-world operation, so the safety profile is covered. The description usefully adds that files are written to the images output folder and returns the written files. It omits meaningful traits for a render job: whether existing files are overwritten, whether the call blocks until done, and expected cost/duration.

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 the scope stated first and the return value second; no filler, no repetition of the tool name.

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 needn't be explained. However, with a block-writing render operation and 0% parameter documentation, the description should cover the -1 sentinel semantics and the interaction with render settings; that omission leaves the agent guessing about how to call it with overrides.

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% — the four parameters (width, height, sampling, transparency) carry only titles and defaults of -1/false, and the description says nothing about them. It does not explain that -1 means 'inherit from render settings' or how these overrides interact with the configured render settings, which is exactly the gap the description should fill.

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?

States a specific verb and resource — render all enabled cameras and passes into the image output folder — and names the destination via render_get: images.outputPath. It is distinguishable from render_image and render_videos by the plural 'cameras and passes' scope, though it never explicitly contrasts itself with 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 statement of when to use this versus render_image, render_videos, or render_export_viewer, and no prerequisite is spelled out (e.g. that cameras/passes must be enabled via render_set_cameras/render_set_passes first). 'Enabled cameras and passes' hints at a precondition but leaves the agent to infer it.

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