Apply a material preset

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

The description clearly states that a new scene is saved, implying the original input scene is not overwritten. This adds useful behavioral context beyond the annotations' destructiveHint=true, which might otherwise suggest the tool modifies the original. It does not disclose error handling for missing presets or object resolution, but the core side-effect is transparent.

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 concise sentence that front-loads the verb 'Resolve' and clearly outlines the three-step action. No filler or redundant information, every word earns its place.

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 output schema exists, return values need not be explained. The description covers the full workflow from preset resolution to final save, and combined with rich parameter descriptions, it is sufficiently complete for an agent to invoke correctly. Minor gaps include object disambiguation (objectName vs objectPath) but this is covered in the schema.

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 each parameter (scenePath, objectName, objectPath, presetName, outputScenePath) having detailed descriptions. The tool description adds no additional parameter semantics, and the baseline for high schema coverage is 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 specifies a clear multi-step action: resolve a preset, apply it to one object, and save a new scene. This distinguishes it from sibling tools like keyshot_apply_material and keyshot_list_material_presets by emphasizing the preset resolution and new scene output.

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 usage for applying a material preset and saving a new scene, but does not explicitly state when to choose this over alternatives like keyshot_apply_material. The parameter description for presetName references keyshot_list_material_presets, giving some context, but no explicit when-not or alternative guidance is provided.

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