Import a model into KeyShot

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds that it applies 'requested composition options' and 'saves a new scene', but does not disclose overwrite behavior or other potential side effects beyond what the schema implies. This is acceptable but not rich.

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 sentence that front-loads the primary action ('Import a supported local model'), specifies the optional base scene, and states the output. It contains no redundant or vague words.

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 tool's moderate complexity, complete schema descriptions, and the presence of an output schema, the description adequately summarizes the workflow. It does not discuss limitations like unsupported formats or error handling, but those are covered by the schema and output schema, and the description is sufficiently complete for an import tool.

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 full descriptions for all 7 parameters (100% coverage), including paths and boolean options. The description's phrase 'apply requested composition options' is a high-level aggregation and adds no detail beyond the schema, so the 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 ('Import') and resource ('a supported local model') and states the outcome ('save a new scene'). It clearly distinguishes this tool from siblings like keyshot_render or keyshot_inspect_scene by focusing solely on the import workflow.

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 indicates when to use the tool: to import a model into either an empty or an existing base scene and then save a new scene. While it does not name explicit alternatives, the scenario is specific enough to guide selection among siblings.

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