obs_create_scene

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

With no annotations, the description carries full responsibility. It discloses that the scene is not switched to, that it is literally empty (no background, audio, or inheritance), and that renaming later has external consequences. These are key behavioral traits that the user must know, and they are all explicitly 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 longer than necessary, but every sentence adds value—addressing behavior, usage, naming, and side effects. It is well-structured and front-loads the core purpose, then elaborates on important nuances. Slightly verbose but not wasteful.

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 and the absence of an output schema, the description covers all essential aspects: the action, non-actions, side effects, naming implications, and subsequent steps. It leaves no critical gaps for the user's decision-making.

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 single parameter 'sceneName' is described simply as 'Name for the new scene,' but the description goes further by explaining uniqueness and its role as an address for other tools. This adds meaningful context beyond the schema's basic type and description, enriching the user's understanding.

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?

Clearly states the action: 'Create a new empty scene.' It specifies the resource (scene) and the nature (empty, new), and distinguishes from related tools like obs_switch_scene by explicitly noting it does not switch. The verb is specific and the scope is unambiguous.

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?

Provides explicit guidance on when to use the tool: 'Build it first with obs_scene_item_add, then switch.' It also cautions about safety ('safe while live') and naming implications, effectively directing users to the appropriate workflow and alternatives.

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