create_scene

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

No annotations provided; description only clarifies the index parameter behavior. Lacks disclosure of side effects, permissions, or impact on existing scenes. Minimal transparency beyond parameter semantics.

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?

Two concise sentences with a bullet for parameters. Front-loaded with the core action and instant clarity on the primary parameter.

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 a simple tool with one optional parameter and an existing output schema, the description sufficiently covers creation intent and parameter behavior. Could mention output or constraints but not critical.

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?

With 0% schema description coverage, the description compensates by explaining the index parameter's effect (-1 appends at end). Adds meaning beyond the schema's default value and title.

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?

Clearly states the tool creates a new scene (Session-view row). Specifies the default index behavior (-1 appends at end). Distinguishes from sibling tools like create_midi_track or create_audio_track.

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 on when to use this tool vs alternatives. Does not mention prerequisites or exclusion cases. Agent must infer usage from the name alone.

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