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

Annotations already declare this is a non-destructive, non-open-world write, so the description's job is to add batch-specific behavior. It does disclose that the identical patch is applied uniformly to every targeted clip, but says nothing about merge-vs-replace semantics for patch fields, atomicity if one clip fails, or any scope limits.

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?

A single front-loaded sentence with zero filler; the batch semantics and an example are conveyed compactly. It is efficient, though arguably too terse given the size of the nested patch 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 mutation tool whose patch object contains dozens of nested styling fields and whose targeting parameters are all optional, one sentence is not enough. The description leaves target selection, merge semantics, and failure behavior undocumented, and there is no output schema to cover the response.

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 25%, so the description should compensate, but it only hints at track-level targeting through the 'on a track' example. The critical ambiguity is unresolved: clipIds and trackId are both optional and the description never says which one selects the targets, what happens if both or neither are supplied, or how nested patch objects are merged into existing clip properties.

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 specific verb and scope: 'Apply the same patch to many clips at once', which is clearly a bulk mutation and implicitly distinguishes it from the singular sibling update_clip. It does not name that sibling explicitly, so the differentiation is inferred rather than stated.

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?

The parenthetical example ('restyle all captions on a track') gives one concrete usage scenario, which is enough to imply when the tool is appropriate. There is no explicit when-not guidance, no mention of using update_clip for a single clip, and no statement about what happens when no target is specified.

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