duplicate_clip_region

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

Annotations already declare this is a non-read-only but non-destructive, closed-world write, and 'copy' is consistent with that. The description usefully narrows behavior to MIDI notes only (not automation or audio) and keeps the result inside the same clip, but it does not say whether notes already at the destination are overwritten or merged, nor whether the action is undoable.

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?

One sentence, front-loaded with the verb, with zero redundant wording. Everything stated is operative.

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?

An output schema exists and annotations cover the safety profile, so the description only needed the operational core, which it delivers. The remaining gap is unit/format guidance for the numeric time parameters, a minor omission given the documented return shape.

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 description coverage is 0%, so the description has to carry the load. It maps region_start/region_length to a 'time range' and clarifies that destination is a beat position, but leaves track_index/clip_index unmentioned and says nothing about the arrangement flag or whether times are in beats or seconds.

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?

Specific verb (copy), specific resource (a time range of a MIDI clip's notes), and an explicit scope boundary (to another beat inside the same clip). That boundary separates it from duplicate_clip_loop and duplicate_to_arrangement without naming them, though the sibling routing is only implicit.

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 when-to-use statement, no prerequisites, and no reference to alternatives such as duplicate_clip_loop, crop_clip, or duplicate_to_arrangement. An agent must infer the choice purely from the one-line scope description.

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