Create scene

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates an 'empty' scene, which is a mild behavioral trait, but it does not mention what happens if the scene name already exists, whether the new scene becomes the current scene, or any other side effects. This is a significant gap 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?

The description is a single, front-loaded sentence with zero waste. It immediately states the purpose without any filler, making it an appropriately sized definition for a tool of this simplicity.

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?

While the tool is simple and an output schema exists, the description leaves out important contextual details such as error behavior (duplicate names), side effects (whether the scene is auto-activated), and the typical workflow of creating a scene before populating it with sources. Given the availability of sibling tools like duplicate_scene, more guidance would be expected.

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 schema has one required parameter, scene_name, and the schema description coverage is 0%. The description adds no meaning beyond the parameter's title, which is already present in the schema. For such a simple parameter, the lack of explanation may be acceptable, but the description does not compensate for the low schema coverage as required.

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') and the resource ('a new empty scene'), which distinguishes it from sibling tools like delete_scene, rename_scene, and duplicate_scene. The word 'empty' adds a useful qualifier that implies a scene with no sources.

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?

No guidance is provided about when to use this tool versus alternatives like duplicate_scene or switch_scene. The description does not mention prerequisites, such as whether creating a scene is required before adding sources, nor does it explain exclusions (e.g., when a scene name already exists).

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