create_scene

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

With no annotations, the description must disclose behavioral traits. It only mentions the index parameter and its semantics, but it does not describe what happens during creation (e.g., scene shifts, effect on other scenes, or whether it returns anything). The output schema exists but is not referenced in the description.

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 two short sentences that front-load the core action and then list the parameter. No unnecessary 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 existence of many scene-related sibling tools and the lack of annotation, the description is incomplete. It does not explain what kind of scene is created (empty? with clips?), the effect on other scenes, or how it relates to similar functions like capture_and_insert_scene.

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?

Schema description coverage is 0%, so the description must compensate. It explains the index parameter as 'Position to insert (-1 = end)', adding meaning beyond the schema's default value and type. However, it does not elaborate on other potential aspects.

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 scene'), making the purpose understandable. It distinguishes from sibling tools like fire_scene, set_scene_name, etc., but does not clarify how it differs from capture_and_insert_scene (which also creates a scene with captured content).

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 explicit guidance on when to use this tool versus alternatives (e.g., capture_and_insert_scene, duplicate_scene). The description implies it is for creating empty scenes, but this is not stated, and no exclusions or context are provided.

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