render_all_cameras

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

No annotations are provided, so the description carries the full responsibility for disclosing behavior. It mentions the side effect that individual renders are deleted if output_dir is omitted, which is useful. However, it does not clarify what exactly the returned contact sheet is (e.g., file path, image data) or mention any potential scene modifications or error conditions.

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 concise and well-structured. It states the purpose in one sentence, then lists parameters with clear explanations. No redundant or tangential information is included.

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 tool with multiple related siblings, the description lacks context about when to use it versus alternatives like 'render_from_camera' or 'capture_contact_sheet'. It also does not mention prerequisite conditions (e.g., cameras in the scene) or error handling, leaving some ambiguity in a broader workflow.

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 contains only titles and defaults, so the description provides the sole explanations for all four parameters: width, height, samples, and output_dir. Each is described with enough context to understand its purpose, fully compensating for the lack of schema descriptions.

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's function: rendering a still from every camera in the scene and returning a contact sheet with labelled results. It uses a specific verb ('render') and specifies the resource ('every camera') and output ('contact sheet'), making its purpose unambiguous.

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?

While the description implies usage when multiple camera renders are needed, it does not explicitly contrast this with similar sibling tools like 'render_from_camera' or 'capture_contact_sheet'. No conditions or prerequisites are mentioned, so guidance on when to choose this tool over alternatives is limited.

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