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

Beyond the annotations, the description discloses the real side effects: the older item leaves the project, clips too short for the new file are truncated and listed, and the whole operation collapses into one undo step. That truncation and removal sit in slight tension with destructiveHint=false, but the explicit one-undo-step reversibility keeps this from being a true contradiction. It does not describe the shape of the result list of shortened clips, though check_edit is offered as the way to inspect them.

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 verb is front-loaded and the whole definition is only three sentences, but the opening sentence is an awkward pile of parentheses and relative clauses ('the newer version of files that have one') that takes a second read to parse. Dense rather than padded, yet readability suffers.

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 mutation tool with no output schema, it covers the essentials an agent needs before calling: what gets changed, what gets removed, what gets truncated, the undo granularity, the default scope, and where to verify. Only the return value for the shortened-clip listing is left implicit.

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 100% and both parameters already document their defaults (every media item with a newer version; the open project), so the schema carries the parameter burden. The description's only added meaning is defining what qualifies as having a newer version, which is a marginal gain over the schema. Baseline 3 is appropriate.

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 gives a concrete verb and resource: move the project's clips onto the newer version of media files that have a newerVersion, and it defines that state as arising after replace_asset or a new library upload. It also scopes the effect (clips, parked takes, old item leaving) so an agent can distinguish it from delete_version or restore_version. It stops short of naming those siblings as exclusions, so it is clear but not fully differentiated.

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?

It establishes the precondition for use (a media item already has a newerVersion from replace_asset or a new upload) and points to check_edit for verifying resulting gaps, which is genuine routing guidance. It does not state when NOT to use it or when delete_version/restore_version would be preferred, so it stops at clear context rather than full exclusions.

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