Render one KeyShot view

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

Annotations already flag destructiveHint=true, and the description adds that it outputs to an image file. However, it does not disclose potential overwriting of outputPath, render time expectations, or license/prerequisite requirements. The description adds minimal behavioral context beyond the annotations, so it meets but does not exceed the baseline.

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, well-structured sentence that front-loads the action and outcome. Every word adds value, with no redundant or filler content.

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 has 9 parameters and multiple render-related siblings, the description is somewhat minimal. It explains the basic purpose but does not guide the agent on when to choose this tool over alternatives or warn about side effects. The presence of a complete output schema and parameter descriptions keeps it at a minimally viable level.

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 100% with detailed per-parameter descriptions (e.g., qualityPreset dimensions and samples, samples vs. maxTimeSeconds conflict). The tool description adds no additional parameter-level meaning, so it does not go beyond what the schema already provides.

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 core action: 'Render the active or a named camera from an existing scene to an image file.' This uses a specific verb ('Render') and resource ('camera from an existing scene'), and the title 'Render one KeyShot view' further distinguishes it from batch or product render 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?

The phrase 'from an existing scene' and 'active or a named camera' implies a single-view render use case, but the description does not explicitly contrast with siblings like keyshot_batch_render, keyshot_preview_render, or keyshot_render_all_cameras. It offers some contextual guidance without naming alternatives or exclusions.

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