trim_clip

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

With no annotations, the description carries the burden, and it does disclose the most important non-obvious trait: the edit ripples the storyline, so downstream clips shift. It omits permission/undo behavior, what happens if trim_start+trim_end exceeds the clip duration, and whether the operation is reversible.

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?

A single sentence, front-loaded with the action and its effect, with zero redundant text. The parenthetical ripple warning is placed exactly where it matters.

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 3-param mutating timeline tool with no annotations and no output schema, the description covers the core edit and its ripple side effect but leaves ref semantics, failure modes, and reversibility 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 0%, so the description must compensate. It does define trim_start and trim_end well — units in seconds and which edge each removes — but the required `ref` parameter is never explained (clip id? timeline index?), leaving one of three params undocumented.

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?

Names a specific verb (shorten/trim), the resource (clip), and the exact mechanism (removing seconds from each end). It separates itself from siblings like delete_clip and split_clip implicitly via the 'ripples the storyline' note, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer 'use this to shorten a clip in place.' There is no guidance on when to prefer trim_clip over cut_ranges, keep_ranges, split_clip, or delete_clip, and no stated preconditions (e.g., clip must be on an open timeline).

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