Prepare and render a product

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

The annotations already declare destructiveHint=true. The description adds useful context such as 'headless process' and 'save a scene copy,' but it does not disclose details about overwrite behavior, error handling in allCameras mode, or what happens to the original scene. This is moderate additional value beyond annotations.

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?

One sentence with a colon-separated list, front-loaded with the action, and every phrase earns its place. No redundant filler or restatement of the title.

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 32 parameters, a single overview sentence is relatively thin. It omits important modes (single vs allCameras), mutual-exclusion constraints (modelPath vs scenePath), and overwrite behavior—though these are all covered in the schema. The description gives a helpful overview but isn't sufficient for an agent to fully understand the workflow without deep schema inspection.

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 100% with every parameter described. The description groups steps (assign materials, configure camera/environment, save scene copy, render) that map to parameter families, but it does not introduce any semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 ('Run') and resource ('complete product workflow'), with a concrete list of steps that clearly distinguishes this from single-purpose sibling tools like keyshot_import_model, keyshot_apply_material, or keyshot_render. It immediately signals the tool's all-in-one scope.

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 'complete product workflow' implies end-to-end use, but the description never explicitly says when to prefer this over individual sibling tools, nor does it mention exclusions or alternatives. Usage context is implied rather than stated, so it earns a 3.

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