obs_studio_mode

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

With no annotations present, the description carries full responsibility for behavioral disclosure. It does this thoroughly: changing studio mode has no viewer-visible effect, it can be enabled mid-broadcast, it affects the operator's OBS window, disabling silently discards the staged preview, and preview requests fail with code 506 while studio mode is off.

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 longer than a minimal tool description, but every sentence earns its place. It is front-loaded with purpose, then explains when to use it, then clearly structures edge cases and traps in a way that is easy for an agent to consume.

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 simple boolean parameter and no output schema, the description is complete enough for reliable tool use. It not only explains the main operation but also provides critical workflow context about preview deletion, direct cuts, and preview request failures, leaving almost no ambiguity for an autonomous agent.

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 already fully covers the single parameter: omit to read, true to enable, false to disable. The description adds good behavioral context about consequences, but it does not add much new meaning to the parameter itself, so the high schema coverage baseline of 3 is appropriate.

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 opens with a precise verb and object: 'Read or set whether OBS is in studio mode.' It explains the PREVIEW/PROGRAM distinction and clearly differentiates this tool from scene-switching tools like obs_switch_scene by emphasizing the reviewed path.

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?

It gives explicit operational guidance: 'If you are going to move scenes automatically, turn this on first.' It also tells the agent when this tool is not sufficient — studio mode does not block direct cuts via obs_switch_scene — and warns about disabling it, including the lost preview and 506 failures.

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