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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so safety is covered. The description adds that one side can be trimmed for J/L cuts and that the return value is the edit result, but it does not elaborate on ripple, other_tracks, or preview behavior beyond what the schema says. With annotations present, this is an adequate but not rich behavioral disclosure.

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?

Two sentences, front-loaded with the core action and with no wasted words. The second sentence packs the J/L cut detail and return-value note efficiently, though it could be slightly clearer about what 'the edit result' entails.

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 tool has 8 parameters (4 required), an output schema, and annotations, so some complexity is handled elsewhere. However, the description omits behavior of ripple, other_tracks, and preview, and gives no differentiation from closely related siblings, leaving meaningful gaps for an agent selecting and invoking this tool.

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 75%, so the schema already documents most parameters, including intricate options like other_tracks and ripple. The description only restates the edge movement and briefly mentions the side parameter for J/L cuts; it adds little beyond the schema's own field descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Move the start or end edge of a clip', which clearly identifies the trimming operation. However, it does not distinguish this from sibling tools like clip.roll, clip.slip, or clip.slide that also alter clip boundaries, leaving an agent to infer the difference.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternatives are named. The mention of 'side: video or audio trims one half of a link group (J/L cuts)' explains a parameter effect but does not help an agent choose between this tool and siblings such as clip.roll or range.extract.

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