set_current_preview_scene

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the 'studio mode only' constraint and the staging purpose, but it does not mention what happens if studio mode is disabled (e.g., error or no-op) or any return value/effects.

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 concise and well-structured. It leads with a clear, informative sentence, then an Args block with the parameter. There is no unnecessary fluff.

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?

For a simple one-parameter tool, the description covers the essential purpose and usage, and the 'studio mode only' caveat is key. It omits error handling details and prerequisites, but given the simplicity, the description is fairly complete.

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 schema has 0% description coverage, so the description must compensate. It includes 'Exact scene name' for the single parameter, which adds a precision qualifier beyond the schema's bare 'Scene Name'. However, it doesn't provide additional context like where to find valid scene names.

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 a specific action ('Load a scene into Preview') with a resource (scene) and context (studio mode only). It distinguishes itself from sibling tools like set_current_program_scene by explicitly targeting Preview and mentioning the follow-up transition.

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 provides clear usage context: studio mode only, and it stages a scene before transitioning to Program via trigger_studio_mode_transition. This implies when to use the tool, though it doesn't explicitly name alternatives such as set_current_program_scene.

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