Create Scene

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

The description does not add any behavioral details beyond the annotations. It does not mention whether creating a scene with an existing name fails, whether it affects the current scene, or any other side effects. The annotations only indicate non-read-only and non-destructive, but the tool's actual behavior remains opaque. The description contributes nothing to transparency.

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 extremely concise with exactly one sentence. It conveys the essential purpose without any fluff or unnecessary detail. It is well-structured for a simple tool.

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 description is too minimal to be complete for a create operation. It does not mention any return value, error conditions, or impact on the scene collection. Since there is no output schema, the description should ideally provide some context about what happens after creation, but it does not. This leaves the agent and users with significant gaps in understanding the full behavior.

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 already provides descriptions for both parameters (sceneName and canvasUuid), so schema coverage is 100%. The tool description does not add any additional meaning or clarify the relationship between the parameters. Since the description itself adds no value beyond the schema, it stays at the baseline score of 3.

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: 'Create a new scene in OBS'. It specifies the verb (create) and the resource (scene), and it is distinct from other scene-related operations like get, set, or remove. It is unambiguous and immediately understandable.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, side effects, or scenarios where it is appropriate. For example, it does not differentiate from creating a scene item or switching scenes. The one-line description offers no usage context.

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