timeline_trim_clip

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool adjusts trim handles; it does not mention that this is an in-place mutation, what constraints apply (e.g., source media bounds), whether subsequent clips are affected, or whether the operation is undoable.

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 compact and front-loaded: the core purpose appears in the first sentence, followed by a clean, minimal Args list. There is no redundant wording 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?

All call parameters are fully explained and an output schema exists, so return format does not need description. However, because this is a mutating timeline operation with no annotations and no behavioral caveats, an agent is left without crucial safety or failure-context information such as valid trim ranges or track/clip existence requirements.

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 fully document parameters, and it does. Each argument receives a clear meaning: track_id identifies the track, clip_index is explicitly 0-based, and in_point/out_point are given in seconds with the crucial 'None = leave unchanged' semantics.

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 uses a specific verb, 'Adjust', and names the exact resource: 'the in/out trim handles of a timeline clip'. The parenthetical 'not the crop filter' immediately disambiguates a likely source of confusion and separates it from sibling clip/filter operations.

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 explicit guidance about when to use this tool versus alternatives such as timeline_split_clip, timeline_move_clip, or filter-based cropping. The 'not the crop filter' note is a useful clarification, but it does not provide actual selection criteria or when-not-to-use conditions.

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