create_scene

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the index parameter (insert position, -1 appends) but does not disclose side effects like whether the new scene becomes selected, how existing scenes shift, or any permissions required. This is minimal transparency for a create operation.

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 concise, containing a one-sentence summary and an 'Args' section for the parameter. It is front-loaded with the main purpose and avoids unnecessary details, making it easy to parse quickly.

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?

The tool is simple (one optional parameter) and has an output schema, so the description doesn't need to explain return values. However, it lacks usage context and behavioral side effects, making it only minimally complete. It adequately covers the action and parameter but leaves out when and how it fits into the broader scene workflow.

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 lists index as an integer with default -1 and no description. The description compensates by explaining that index is the position to insert the scene and that -1 appends at the end. This adds meaningful clarity for the sole parameter, fully covering its basic semantics.

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 'Create' and the resource 'a new scene in the session', which is specific and distinct from sibling tools like duplicate_scene, delete_scene, or set_scene_name. It immediately conveys the tool's core function.

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, such as duplicate_scene or set_scene_name. It lacks any context about typical use cases, prerequisites, or situations where this tool is preferred.

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