duplicate_clip_to_scene

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

No annotations provided, so description carries full burden. It specifies constraints (src has clip, dest empty) but does not disclose side effects, permission requirements, reversibility, or whether the copy modifies the original or triggers playback. This is insufficient for a mutation tool.

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 with no wasted words. It starts with a clear purpose, adds a practical use case, then lists parameters with required conditions. Well-organized and efficient.

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 three parameters and a simple copy operation, the description covers the core semantics. It does not explain return values, but an output schema exists (though not shown) reducing the burden. Minor gap: no mention of success/failure or error cases.

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?

Schema coverage is 0%, so description must compensate. It describes all three parameters with meaningful context: track_index as owning track, src_clip_index as source slot (must contain clip), dest_clip_index as target slot (must be empty). This adds significant value over the schema's bare titles.

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 it copies a clip (MIDI or AUDIO) from one slot to another empty slot on the same track. It explicitly contrasts with create_clip by noting it works for audio clips too, distinguishing it from siblings.

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?

It provides explicit use case: 'place a loop into several scenes for live performance'. It states prerequisites (src must contain a clip, dest must be empty). However, it does not explicitly list alternatives or when not to use it, though the comparison to create_clip offers some guidance.

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