trim_clip

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the basic mutation (adjusting in/out points) but does not explain whether the trim is a ripple edit, whether adjacent clips are affected, whether inPoint and outPoint/duration have precedence rules, or what happens if the values exceed the clip's media bounds.

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 sentence with no filler, front-loading the main action and resource. It is appropriately concise for a straightforward tool.

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?

The description plus schema provide a usable definition for a simple trim, but the lack of any usage guidance or behavioral disclosure around ripple behavior and trim semantics leaves gaps. Given the large sibling set and absent annotations, a bit more operational context would be needed for confident invocation.

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 100%, so the schema already documents each parameter's meaning and the mutual exclusivity of duration and outPoint. The description adds no additional parameter-level nuance beyond what the schema provides, which is acceptable but not additive.

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 identifies the tool as adjusting a clip's in and out points on the timeline and notes the resulting effect ('effectively shortening it'). This distinguishes it from vague editing verbs, though it does not explicitly contrast it with related trim-family tools like ripple_delete or roll_edit.

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?

There is no guidance on when to use this tool versus the many sibling tools that manipulate clips, such as split_clip, ripple_delete, roll_edit, slide_edit, or slip_edit. The description implies a basic trim operation but provides no conditions, exclusions, or alternative tool references.

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