keyshot_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 burden for behavioral disclosure. It states the tool discovers cameras and renders them, but does not explain how it handles errors, whether rendering is sequential or parallel, output file naming conventions, or any side effects. The presence of parameters like 'continueOnError' and 'overwrite' suggests important behaviors that are not mentioned.

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, concise sentence that is front-loaded with the core purpose. However, for a tool with 9 parameters and no annotations, it is too terse and sacrifices necessary detail for brevity. It earns a middle score as it is not verbose but is under-specified.

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 the tool's complexity (9 parameters, no output schema, no annotations), the description is grossly incomplete. It fails to explain how the output is organized, default values for optional parameters, behavior of flags like overwrite and continueOnError, or return results. A complete description would need to address these gaps.

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%, meaning the description adds no parameter-level information. It only implies 'scenePath' and 'outputDir' from the main sentence, but does not explain any other parameters (width, height, samples, format, overwrite, maxTimeSeconds, continueOnError). An agent cannot infer parameter semantics from this description alone.

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 discovers every camera in a KeyShot scene and renders each view to an output directory. It uses specific verbs ('discover', 'render') and resource ('cameras in one KeyShot scene'), and distinguishes itself from siblings like keyshot_list_cameras (which only lists) and keyshot_render (which renders a single view).

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or any exclusion criteria. There is no reference to sibling tools or scenarios where a more targeted tool like keyshot_render or keyshot_list_cameras would be preferable.

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