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

Annotations declare this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is already covered. The description adds real behavioral context beyond that by explaining exactly what ripple=true does to the rest of the track and why (no gap opens), which is the key non-obvious trait. It stops short of disclosing what happens to trimmed-away content, whether trimming is reversible via undo, or error cases such as start exceeding end.

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 tight sentences with the core action front-loaded and the ripple semantics immediately after, with no filler. The parenthetical '(the in-point follows)' is slightly ambiguous phrasing but carries useful meaning, so nothing is clearly wasteful.

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 five-parameter mutation tool with no output schema, the description covers the action, the two edge parameters, and the ripple flag well enough to call it correctly. It leaves out error behavior and the effect on neighboring clips beyond the ripple case, which keeps it short of fully complete.

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%, with just projectId documented, so the description must compensate and largely does: it explains that start and end refer to the timeline edges, that either may be set independently, that the in-point follows, and it defines ripple's effect precisely. clipId is left implicit, which is a minor gap given it is the sole required parameter.

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 states a specific verb-plus-resource: setting a clip's timeline start and/or end edge, which reads clearly as a trim operation. It does not, however, differentiate itself from nearby siblings such as slip_clip, move_clip, or split_clip, so an agent must infer the distinction from the word 'trim' alone.

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 this is the tool for changing a clip's in/out points, and the ripple explanation gives a clue about when to enable it. There is no explicit statement of when to prefer this over slip_clip or move_clip, and no stated preconditions or exclusions.

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