Switch scene collection

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

With no annotations provided, the description carries the full burden. It adds 'High impact' as a warning, but does not specify what the impact is (e.g., replacing all current scenes, potentially disrupting active recordings). This is vague and insufficient for a mutation tool.

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?

Two short sentences, front-loaded with the purpose. Every word earns its place, and the 'High impact' warning adds value without bloat.

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?

The tool has two parameters, one required, and a high-impact warning, but the description provides no specifics about parameter usage or consequences of the action. The output schema exists, so return values are not needed, but the description is still incomplete for a setter with such a warning.

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?

Schema description coverage is 0%, and the description does not mention either parameter. 'collection_name' is required but its meaning or expected format is not explained, and 'confirm' is entirely omitted. No compensating information is provided.

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 'Switch to another OBS scene collection' uses a specific verb and resource, clearly distinguishing it from sibling tools like switch_scene (which switches to another scene within the current collection) and list_scene_collections (which lists collections).

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 states the action but does not explicitly mention when to use this tool versus alternatives. 'High impact' implies caution, but there are no clear exclusions or alternative references, so usage guidance is only implied.

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