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 does not state whether the new scene becomes selected, how existing scenes are affected, whether the operation is undoable, or what the return value is. The index parameter is explained, but broader side effects remain opaque.

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: one clear sentence plus a parameter list. It is front-loaded and contains no filler, repetition, or extraneous information.

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?

For a simple creation tool, the description covers the parameter adequately, but lacks context about return values and side effects. With no output schema or annotations, the agent is left without a complete picture of what happens after invocation. It is acceptable as a minimum viable description but has clear gaps.

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 description explicitly defines the 'index' parameter with a special sentinel value (-1 = end of list), adding meaning beyond the bare schema type and default. Since schema description coverage is 0%, this explanation is essential and effectively compensates for the only parameter.

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 verb-resource pair ('Create a new scene') and includes the index parameter context. It distinguishes from sibling operations like duplicate_scene by focusing on new scene creation, though it could more explicitly state what 'scene' means in this context.

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 on when to use this tool versus alternatives such as fire_scene, select_scene, or delete_scene. The description gives no context for appropriate usage or exclusions, leaving the agent to infer applicability.

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