Move clip

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

With no annotations the description carries the full burden, and it does disclose meaningful behavior: the "new" value for to_track creates a track (a side effect), omitting to preserves the current position, and a non-unique address is an error. It does not mention permissions, undo, or how overlapping clips are handled on the target track.

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?

Front-loaded with the core action and then the addressing rules, with almost no filler. The closing sentence partially restates the earlier "without to the clip keeps its position" point, costing a little density.

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 7-parameter mutation tool with no annotations and no output schema, the description covers addressing, defaults, the create-track side effect, and the required-argument rule. It stops short of describing collision behavior on the destination track or the tool's result.

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 already 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint not expressed in the schema: at least one of to and to_track must be supplied, and at/region are alternative addressing modes.

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?

States a specific verb and resource ("Moves one clip") and clarifies the two dimensions of movement: timeline position and/or track. It does not differentiate itself from the sibling place_clip, so an agent must infer the split between moving an existing clip and placing one.

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?

Gives operational constraints ("the address must match exactly one clip", "Give at least one of to and to_track") but never states when to choose this over place_clip or remove_clip. The guidance is about how to call it, not when to prefer it.

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