capture_and_insert_scene

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

The description 'snapshot ... into a new scene' is non-destructive, consistent with destructiveHint: false. It adds context about capturing current playing clips but does not detail edge cases (e.g., no clips playing) or naming conventions.

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, concise sentence that immediately conveys the action and context. 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 tool has zero parameters and an output schema exists, the description provides essential information. It could mention what happens if no clips are playing or how the new scene is named, but overall it is fairly complete.

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?

No parameters are present (schema coverage 100%). The description adds meaning by explaining the tool's purpose, which is sufficient since no parameter details are needed.

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 tool's action: 'Snapshot the currently playing Session clips into a new scene'. The phrase 'keep that combination' workflow distinguishes it from siblings like 'create_scene' (which creates an empty scene) and 'fire_scene' (which triggers playback).

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 implies usage via 'keep that combination' workflow, suggesting it is for preserving current clip arrangements. However, it does not explicitly state when to use this over alternatives like 'create_scene' or when not to use it.

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