capture_and_insert_scene

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

With no annotations provided, the description carries the burden. It discloses the primary action (creating a new scene containing currently playing session clips), but does not mention potential side effects like whether existing clips are stopped or whether the new scene is inserted at a specific position. The description is minimal and lacks deeper behavioral context, but it does state the core behavior clearly.

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 and front-loaded: two short sentences that state the action and clarify it. Every word earns its place, with no redundancy or unnecessary detail.

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 zero-parameter tool, the description is reasonably complete, clearly stating what the tool does and the context (session clips). It does not explain edge cases like what happens if no clips are playing, but the presence of an output schema likely covers return values. Given the simplicity of the tool, the description is adequate.

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 tool has no parameters, and the input schema is an empty object. The description therefore does not need to explain parameter semantics; it appropriately focuses on the tool's behavior. A baseline of 4 is appropriate given zero parameters.

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 function: capturing currently playing clips into a new scene. The verb 'Capture' and resource 'currently playing clips into a new scene' are specific, and it distinguishes itself from related tools like 'create_scene' (which likely creates an empty scene) and 'capture_midi' (which captures MIDI).

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: when you want to create a new scene from currently playing session clips. However, it does not explicitly mention when to use this tool versus alternatives like 'capture_midi' or 'create_scene', nor does it note conditions like requiring playing clips or exclusions.

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