Pause or resume the real-time view in KeyShot Studio to control live updates during renders; the view can restart automatically if it was active before.
Met en pause ou relance la vue temps réel (bouton « Pause » de la barre d'outils). Le pont la relance de lui-même après ses rendus si elle tournait avant.
| Name | Required | Description | Default |
|---|---|---|---|
| paused | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare the safety profile (not read-only, not destructive, closed-world); the description adds genuine behavioral context beyond that — this acts as a toggle and the view auto-restarts after renders when it was running before. That is non-obvious state behavior the annotations do not convey.
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?
Two tight sentences, with the core action front-loaded before the auto-restart caveat. Nothing is padded, though the parenthetical UI reference is only marginally useful to an agent.
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 an output schema present, return values need no explanation, and the safety profile comes from annotations. For a single-boolean toggle the description covers the essential behavior; only the boolean polarity is left implicit.
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 0% for the single required `paused` boolean. The description's 'met en pause ou relance' frames the toggle semantics, letting an agent infer true = pause, but it never states the mapping or the default state explicitly.
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 names a specific action (pause or resume) on a specific resource (the real-time view), and anchors it to a concrete UI control (the 'Pause' toolbar button). An agent can tell this apart from render/image siblings without opening the schema, though it never explicitly contrasts itself with any of them.
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 second sentence supplies real usage context: the bridge re-enables real-time view on its own after renders if it was previously running, so an agent knows it need not call this to restore the view after a render. There is no explicit statement of when-not-to-call or a named alternative, keeping it 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.