Sync the latest saved KeyShot scene

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

Annotations already flag destructiveHint=true, lowering the burden. The description adds useful behavioral context: it detects changes, copies to a collision-safe path (avoiding overwrites), and optionally returns a preview. It also notes the tool is a stable alternative to GUI control, giving insight into its operating style. No contradictions with 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 two sentences, front-loaded with the core workflow, and contains no filler. It efficiently conveys the main actions and the key differentiator (stable alternative to GUI control) without redundancy.

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?

With 9 parameters and an output schema, the description provides a solid high-level overview of the workflow, covering the main steps and the preview option. It does not delve into all edge cases, but the schema and output schema fill in the necessary detail. The description is complete enough for an agent to understand the tool's role and scope.

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%, so the baseline is 3. The description's reference to 'collision-safe output path' and 'detect whether it changed' aligns with outputScenePath and previousFingerprint, but it does not add additional meaning beyond the schema. The schema already explains all parameters clearly, so the description adds minimal incremental value.

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: find a .bip file, detect changes, copy to a collision-safe path, and optionally generate a preview. It names the specific resource (.bip) and scope (newest in one folder). It also distinguishes itself as the stable alternative to unsupported persistent GUI control, setting it apart from sibling tools focused on rendering or scene inspection.

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 when syncing saved KeyShot scenes is needed and positions it as an alternative to GUI control. However, it does not explicitly state when to use this tool versus sibling tools like keyshot_save_scene or keyshot_inspect_scene, and gives no exclusion criteria. The guidance is implied rather than explicit.

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