open_obs

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

The description discloses some behavioral traits: it opens OBS only 'if necessary' and optionally selects a scene. However, it does not detail side effects (e.g., window focus, scene switching) or error scenarios. Since annotations indicate a mutation (readOnlyHint=false), the description adds a bit of context but not rich behavioral depth.

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, concise sentence that front-loads the primary action ('Open OBS') and efficiently adds the optional scene selection. Every word earns its place with no redundancy.

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 tool's simplicity (2 optional params, no output schema), the description covers the core functionality but leaves gaps: what 'configured' scene means, how 'if necessary' is determined, and what timeout_ms controls. It is adequate for a basic tool but not fully 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 description coverage is 0%, and the description fails to explain the parameters. It hints at 'target' via 'emulator or physical-device scene' but does not clarify that target is optional (no required params) or describe the purpose/meaning of timeout_ms. The description does not compensate for the lack of schema documentation.

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: 'Open OBS if necessary and optionally select the configured emulator or physical-device scene.' It uses a specific verb ('Open') and resource ('OBS'), and the optional scene selection differentiates it from sibling tools like get_obs_status or start_obs_recording.

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 implied usage context ('if necessary') but does not explicitly state when to use this tool versus alternatives such as get_obs_status or start_obs_recording. It lacks clear when-to-use or when-not-to-use guidance, making it adequate but not explicit.

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