obs-trigger-studio-transition

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

No annotations are provided, so the description carries the full burden. It states the action ('Trigger a transition') but doesn't disclose behavioral traits such as whether this requires Studio Mode to be enabled, if it's idempotent, what happens on failure, or any side effects. The description is minimal and lacks crucial operational context.

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 a single, direct sentence that efficiently conveys the core action and context without any wasted words. It is front-loaded and appropriately sized for a tool with no parameters.

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 complexity of triggering a transition in a broadcasting context, the description is incomplete. No annotations, no output schema, and minimal behavioral disclosure leave gaps in understanding prerequisites, effects, or error handling. It should provide more context for safe and effective use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned if any implicit parameters or context are required. Baseline is high due to no parameters.

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 action ('Trigger a transition') and the specific context ('from preview to program scene in Studio Mode'), making the purpose evident. However, it doesn't explicitly distinguish this tool from the sibling 'obs-trigger-transition', which might handle general transitions, leaving some ambiguity about sibling differentiation.

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 in OBS Studio Mode when transitioning from preview to program, but it doesn't specify when to use this versus alternatives like 'obs-trigger-transition' or other scene-setting tools. No explicit exclusions or prerequisites are mentioned, relying on contextual inference.

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