Export Sequence Clip Review Frames

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

Annotations are thin (mostly negative hints), so the description carries real weight: it discloses that this is one bridge request, that frames are file-verified, and that it does not mute tracks or claim visual quality. The 'Read-only in Premiere' line usefully scopes the write (files to output_dir) away from project mutation, consistent with readOnlyHint=false.

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 sentences, front-loaded with the core action and scope, with no filler. The trailing 'does not mute tracks or claim visual quality' clause is slightly defensive but still earns its place as a disambiguation.

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?

With an output schema present, return values need no explanation, and the description covers the key operating facts (midpoint sampling, track selection, single bridge request, no project mutation). The batch-size behavior is left entirely to the schema, but nothing critical for correct invocation is missing.

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 every parameter (output_dir, track_index, limit) is documented in the schema, so the baseline is 3. The description adds the 'chosen video track' and midpoint context but no new semantics for limit or output_dir doubling.

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 (export) and resource (one file-verified still frame at the midpoint of each clip on a chosen video track), which inherently separates it from marker-based siblings and capture_frame. It does not name the closest siblings (export_sequence_review_frames, export_sequence_marker_review_frames) to sharpen the choice.

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 'midpoint of each clip on a chosen video track' scope implies when this tool is appropriate, but there is no explicit when-to-use or when-not guidance, and no sibling alternative is named despite several near-identical export tools in the list.

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