keyshot_apply_camera_preset

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

The description discloses that the tool creates/updates a camera and saves the scene, implying state changes. However, it does not specify permissions, reversibility, or whether the outputScenePath overwrites an existing file. With no annotations, these gaps reduce transparency.

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?

Single sentence with 16 words, no redundancy, clearly conveys the core action. Highly efficient and front-loaded.

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 4 parameters and no output schema, the description is overly minimal. It omits how optional parameters like 'cameraName' are handled, what constitutes a valid preset, and the effect on the scene file. Incomplete for effective use.

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 input schema has 4 parameters with 0% description coverage, and the description provides no additional information about any parameter. The agent must guess the meaning of 'cameraName', 'presetName', etc., which is insufficient.

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 action ('Create or update a named camera from a standard or custom camera preset') and the resource ('scene'), distinguishing it from sibling tools like 'keyshot_set_camera' which does not use presets. The mention of saving the scene adds specificity.

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?

No guidance on when to use this tool versus alternatives like 'keyshot_set_camera' or 'keyshot_apply_material_preset'. No prerequisites, exclusions, or context of use are provided.

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