Render selected cameras

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which the description does not contradict. The description adds that output goes to a directory but does not disclose additional behavioral details like overwrite rules, rendering time, or process requirements, though the schema covers overwrite.

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 sentence that immediately states the action and scope. It contains no filler or redundant information.

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?

Despite being brief, the tool is well-specified through its rich schema (100% parameter coverage), annotations, and output schema. The description provides a clear overview; however, it omits explicit guidance on when to use this vs. sibling render tools, which is a minor gap.

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?

All 10 parameters have schema descriptions, and the schema provides detailed semantics (e.g., overlapping samples/maxTimeSeconds, outputDir path restrictions, qualityPreset values). The tool description itself adds no parameter-specific meaning beyond saying 'explicit list of saved cameras'.

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 uses a specific verb 'Render' and identifies the resource: 'explicit list of saved cameras from one scene' into an output directory. This clearly distinguishes it from siblings like keyshot_render_all_cameras (all cameras) and keyshot_preview_render.

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 for batch-rendering specific cameras but does not explicitly state when to choose this over alternatives such as keyshot_render_all_cameras or keyshot_preview_render. The 'cameras' parameter schema adds a prerequisite ('Use keyshot_list_cameras first') but this is not in the tool description.

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