render_all_cameras

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

Without annotations, the description carries the full burden. It discloses that it renders all cameras simultaneously, returns a composite contact sheet, saves individual renders to a directory, and describes parameter effects (e.g., samples ignored for EEVEE). It could mention potential performance impact or if scene state is altered.

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 short, with the main purpose front-loaded in the first sentence. Each subsequent sentence adds value (parameter details, return info). No wasted words.

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 no output schema, the description explains what is returned (contact sheet) and that individual renders are saved. It could clarify the format of the contact sheet (e.g., image file) but is otherwise sufficient for invocation.

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 coverage is 0%, so the description adds all parameter meaning: width/height (defaults, per camera), samples (ignored for EEVEE), output_dir (temp dir if omitted). This adds significant value beyond the schema which only has names and types.

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 the tool renders a still from every camera simultaneously and returns a contact sheet with labels. This distinguishes it from siblings like 'render_from_camera' (single camera) and 'capture_contact_sheet' (likely viewport-based).

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 implies usage through parameter descriptions but does not explicitly state when to use this tool over alternatives like 'render_from_camera' for single renders or 'capture_contact_sheet' for viewport captures.

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