set_current_program_scene

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions switching the live program scene and that the scene name must be exact, but does not disclose potential errors, side effects, or whether it affects transitions or studio mode.

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 extremely concise, with the action stated upfront and an Args section that covers the parameter without filler. Every sentence adds value, making it easy for an agent to parse quickly.

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 tool with one parameter and no output schema, the description provides the essential purpose and parameter semantics. However, it lacks details on failure behavior (e.g., non-existent scene) and any side effects, which would be useful given the lack of annotations.

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 zero coverage (no param description), but the description compensates by explaining scene_name as 'Exact scene name (see get_scene_list).' This gives crucial guidance: exact match required and how to obtain valid values, which is sufficient for a single-parameter tool.

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 purpose: 'Switch the live Program scene — the core "cut to this scene" action.' This uses a specific verb and resource, and distinguishes it from siblings like set_current_preview_scene by emphasizing the live program and cut action.

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 gives clear context that this is the 'core cut' action and refers to get_scene_list for valid names, implying when to use it. However, it does not explicitly contrast with alternatives like set_current_preview_scene or state when not to use this tool.

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