create_scene

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool creates a new, empty scene but gives no details about naming conflicts, side effects, permissions, or failure modes. This is minimal behavioral information, though not misleading.

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 clear sentence followed by a concise Args block. It contains no unnecessary words and is well-structured for the simple nature of the 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?

Given the tool's simplicity (one parameter, no annotations, no output schema), the description is minimal but lacks important context such as uniqueness requirements for scene names, what 'empty' specifically means in OBS, and whether the operation can fail or overwrite. It does not provide enough surrounding context for an agent to anticipate edge cases.

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 only provides a title 'Scene Name' with no description field (0% coverage). The description adds 'Name for the new scene,' which clearly explains the purpose of the scene_name parameter and compensates for the missing schema description. For a simple string parameter, this is sufficient.

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 'Create a new, empty scene' with a specific verb and resource. It distinguishes itself from related tools like create_scene_collection (which creates a collection of scenes) and create_input (which creates an input).

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 scenarios where creating a scene is appropriate, nor does it reference related operations like renaming or removing scenes. The usage is only implied by the action itself.

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