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

Annotations already declare this is a non-readOnly, non-destructive, closed-world mutation, so the safety profile is covered. The description usefully discloses the default attribute set (everything except keyframes and text style), but it does not say whether target clips' existing attributes are overwritten or merged, nor where the source comes from when both `from` and `fromClipId` could apply.

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, front-loaded with the purpose before the parameter enumeration. The attribute list is long but genuinely informative; the only weakness is the slightly clipped 'attributes:' fragment that reads like a schema echo rather than prose.

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 5-parameter mutation with 40% schema coverage and no output schema, the description covers the attribute dimension well but leaves the source-selection model and the overwrite semantics unexplained. An agent could call it successfully for the common case but would be guessing on `from` vs `fromClipId` and on what happens to attributes not listed.

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 40%, so the description has to compensate. It does add real meaning for `attributes` — enumerating the valid values and stating the default, which the schema omits. However, `clipIds`, `fromClipId`, and especially the relationship between `from` (described in schema as 'the editor clipboard') and `fromClipId` are left unexplained.

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?

"Copy the look of one clip onto others" gives a specific verb and resource, and scopes it to visual/audio attributes rather than whole clips. It does not distinguish itself from nearby siblings such as copy_effects, clear_effects, or paste_clips, so the agent must infer the difference from names 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 implied by the phrasing (use it when you want to replicate a clip's attributes onto other clips), but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent when to prefer this over copy_effects or paste_clips, which is a real ambiguity given such a dense sibling set.

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