Apply a camera preset

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

Annotations already flag destructiveHint=true, and the description adds the dual action of applying and saving, plus 'create or update' implying potential overwrite of existing camera names. However, it doesn't disclose file overwrite specifics or required permissions, so it adds only modest context 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?

The description is a single, well-structured sentence with no filler. It front-loads the action and outcome, making it efficient and easy to parse.

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 schema's 100% parameter coverage and presence of an output schema, the description sufficiently covers the main workflow. Minor ambiguity in 'configured standard-view or absolute camera preset' is clarified by the schema's presetName description, making it adequately complete for a tool with strong annotations.

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 each parameter described. The tool description's high-level summary maps to parameters but doesn't add details beyond the schema, justifying the baseline score of 3.

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 tool's function: create/update a saved camera from a preset and save the scene. It uses specific verbs and resources ('create or update', 'camera preset', 'save the edited scene') and distinguishes from siblings like keyshot_set_camera or keyshot_save_scene by combining both actions.

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 a combined workflow (apply preset and save) and hints at using keyshot_list_camera_presets via the presetName schema description. However, it does not explicitly name alternatives or when-not-to-use conditions, so it falls short of a 5.

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