Create Scene Collection

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

Annotations only indicate readOnly=false and do not provide much behavioral context. The description adds a valuable side-effect disclosure: creating the collection also switches to it. It does not cover edge cases like duplicate names, but for a simple creation tool the main behavioral trait is clearly stated.

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, front-loaded sentence with no filler. It states the action, the resource, and the important side effect in minimal words.

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—one required parameter, no nested objects, no output schema—the description is nearly complete. It states the core action and the side effect. It could go slightly further by noting behavior on duplicate names or whether an error is returned, but that is not essential for basic invocation.

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?

One parameter is documented in the schema with 100% coverage: sceneCollectionName is described as 'Name for the new scene collection.' The description adds no parameter-specific meaning, but because the schema fully covers the parameter, the 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 uses a specific verb ('Creates') and a clear resource ('scene collection'), plus the key behavioral detail that it switches to the new collection. This distinguishes it from sibling tools like obs-set-current-scene-collection, which switches to an existing collection, and obs-get-scene-collection-list, 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 usage is implied: use this tool when you need a new scene collection and want to switch to it immediately. However, there is no explicit guidance about when not to use it or which sibling alternative to choose, such as obs-set-current-scene-collection for switching to an existing collection.

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