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

With only readOnlyHint=false available, the description carries real weight: it discloses that the clip id is preserved, that source in/out move in sync, and enumerates three explicit refusal conditions (under 100ms, crossing a neighbour, exceeding source media). It stops short of saying whether the trim ripples later clips or leaves a gap, and says nothing about undo/reversibility.

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?

Three tight sentences with the core operation front-loaded, followed by the semantic effect and then the failure conditions. No filler and nothing repeated from the title or schema.

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 one-shot mutation with four required params and no output schema, the description covers the mechanics and the error cases an agent needs. The remaining gaps — ripple vs gap behavior toward downstream clips on the same track, and what the call returns — are worth stating but not disqualifying.

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 coverage is 50% (project_id and at_ms are documented; clip_id and edge are not). The description reinforces that at_ms is an absolute TIMELINE position rather than an offset, which duplicates the schema's own note, and implies the edge enum via 'start or end'. It adds no format or constraint detail for clip_id and is largely redundant with the existing schema text.

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 names a specific verb (trim) plus resource (a timeline clip's start or end edge) and the unit of measure (absolute TIMELINE millisecond), so the operation is unambiguous. It does not, however, distinguish itself from the closely related edge-editing siblings (studio.roll_edit, studio.slide_edit, studio.slip_edit, studio.cut_range), which an agent must choose between.

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 implied by the stated effect (source in/out points move with the edge) but there is no explicit guidance on when to pick this over the other trim/edit tools in the studio family. The refusal conditions describe limits, not selection criteria against alternatives.

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