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

Annotations already cover the safety profile (idempotentHint=true, destructiveHint=false, openWorldHint=false), and the description adds the real behavioral consequence that linked clips move/trim/split as a unit. However, it is silent on what happens when clips are already linked, what happens on partial failure, or why idempotency holds, and it punts the return details to "the server instructions."

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 short sentences with the behavioral effect front-loaded, which is good. The second sentence is largely a deflection to external server instructions rather than information, so it only partly earns its place.

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 mutating edit operation with three parameters and an output schema, the description is thin: it does not explain the clip_ids semantics, the effect on already-linked clips, or the new timeline handle returned by the edit. Deferring to "server instructions" leaves the definition incomplete on its own.

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 67%: timeline_id and preview are documented in-schema, but clip_ids — the core parameter — has only a minItems=2 constraint and no explanation in either place. The description says nothing about any parameter, so it fails to compensate for that gap.

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?

"Make clips move, trim and split together" describes the effect of linking, which is more informative than the title alone, but it never states the action verb ("link") or names the sibling it inverts, clip.unlink. An agent can infer the purpose but must reason to it rather than read it directly.

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 when-to-use or when-not-to-use guidance and no mention of the obvious alternative, clip.unlink, which appears in the sibling list. Usage is only implied by the description of what linking does.

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