Set a KeyShot camera

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

Annotations already indicate destructiveHint=true and readOnly=false, and the description aligns by stating 'create or update' and 'save the edited scene.' However, it does not disclose additional behavioral details like whether an existing scene is overwritten or if any permissions/validations apply, so it only minimally adds transparency beyond the 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?

The description is a single, well-structured sentence with the action verb front-loaded. It avoids filler and directly states the purpose, making it highly concise and readable.

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 detailed schema with 100% parameter coverage and the presence of an output schema, the description sufficiently covers the primary action. Minor gaps exist around usage versus camera-preset tools, but the high-quality schema information compensates, making the description adequately complete.

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 description coverage is 100% with per-property explanations, including constraints like position/lookAt pairing and fieldOfView/focalLength exclusion. The description merely lists the parameter categories and does not add meaningful semantics beyond what the schema already provides, so a baseline score of 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--create or update--and identifies the resource as a named camera, with the adjustable parameters listed. It clearly distinguishes itself from sibling tools like keyshot_list_cameras or keyshot_apply_camera_preset by emphasizing direct camera configuration and scene saving.

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 clearly implies the tool is for directly configuring a camera and saving the result, but it does not explicitly address when to use it instead of alternatives such as applying a camera preset. The absence of explicit exclusions keeps it from a perfect score, though the context is unambiguous.

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