move_clip

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

With no annotations, the description must fully disclose behavior. It states 'move' and 'does not ripple', but omits details like what happens if the target time is occupied (overlap handling), scope (all track types), or whether the operation is reversible. Partially transparent.

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 a single concise sentence, but it sacrifices completeness for brevity. It does not address parameter semantics or provide usage context, making it under-informative despite being short.

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 5 parameters, no output schema, and no annotations, the description is insufficient. It only covers basic purpose and a key behavioral trait, leaving parameter roles, return values, and error conditions unaddressed.

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 only 20% (only trackType has a description). The tool description does not explain any of the 5 parameters, leaving meaning ambiguous for clipIndex, trackIndex, newStartSeconds, and sequenceName.

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 the verb 'move' and resource 'timeline clip', and specifies the action: to a new start time on the same track. It also notes a key constraint ('does not ripple other clips'), which distinguishes it from siblings like insert_clip that cause rippling.

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 implies usage for moving clips without affecting adjacent clips, but it does not explicitly state when to use this tool versus alternatives (e.g., insert_clip for rippling moves). No direct guidance on prerequisites or limitations.

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