Save a KeyShot scene copy

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

Annotations already declare destructiveHint=true, so the tool is known to be potentially destructive. The description adds the safe output directory constraint but does not disclose whether the original scene is modified, whether files may be overwritten, or what side effects opening the scene has on the current session.

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, focused sentence that immediately states the tool's purpose and key constraint. There is no unnecessary wording or repetition 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?

The tool is simple with only two parameters, a detailed schema, and a truthful annotation set. The description covers the essential behavior (open, save copy to allowed path). It lacks explicit mention of side effects (e.g., overwriting, effect on current scene), but these are partially covered by the destructiveHint annotation and the output schema would explain results.

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 both parameters already documented in the schema. The description adds the safe directory requirement for outputScenePath, but this is also present in the schema. It does not add further semantic value beyond the structured fields.

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 ('save a copy') and the resource (a KeyShot scene), and specifies the destination constraint (inside the configured safe output directory). This distinguishes it from sibling tools like keyshot_render or keyshot_import_model.

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 usage is implied by the description and name, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions. It does not mention for example 'use keyshot_inspect_scene to view without saving'.

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