move_clips_tool

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

With no annotations, the description must carry behavioral disclosure. It does so by stating 'no neighbor ripple', explaining that inter-track moves preserve media via source_id, and explicitly noting it does not cut a range across dialogue lanes. This adds meaningful behavioral context beyond the tool name, though it does not cover every mutation side effect.

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?

Three short, focused sentences with code formatting. The main purpose is front-loaded, and every sentence adds useful information without repetition or filler.

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 the output schema exists and the operation is a relatively focused move action, the description covers purpose, the main parameter format, key behavioral nuances, and the relevant sibling distinction. It is not exhaustive about edge cases or side effects, but it is strong enough for an agent to select and call the tool correctly.

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%, but the description compensates for the key parameter by specifying that clips_json is a JSON array of objects with clip_id, timeline_start, and track_id. project_path is left to inference from its name, but the complex parameter is meaningfully documented.

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 opens with a specific verb and resource: 'Move clips in session time and/or onto another track'. It also distinguishes itself from move_segment_tool by noting it does not cut a range on every dialogue lane, so an agent can tell it apart from closely related 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?

The description gives clear context for when this tool applies, and it explicitly names move_segment_tool as the contrasting alternative. It does not provide a full when-to-use/when-not-to-use rule set, but the differentiation is strong and actionable.

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