duplicate_to_arrangement

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

No annotations provided, so description carries the burden. It explains the clip is placed on the same track and uses Live's API, but does not cover error cases (invalid indices, empty clip) or side effects (overwriting existing clips).

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?

Well-structured with a brief summary, API note, workflow, and parameter list. No unnecessary information; every sentence adds value.

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 tool with 3 parameters and a clear purpose, the description covers typical usage and workflow. Output schema may provide return info, so omission is acceptable. Still, error handling and edge cases are missing.

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?

Input schema has 0% description coverage, so description adds value by explaining each parameter's meaning and providing example values for destination_time (e.g., 0.0 = start, 8.0 = bar 3).

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 it copies a Session-view clip into the Arrangement timeline. Specifies the API used and placement at destination_time beats. Distinguishes from sibling duplicate_clip_to_scene.

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?

Provides a typical workflow (create clip, duplicate, switch view) that clarifies when to use this tool. Implicitly excludes other scenarios like inter-track duplication.

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