Export Sequence Clip Review Frames

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

The description adds useful behavioral context beyond the annotations: it is read-only with respect to the Premiere project, does not mute tracks, and does not claim visual quality. These caveats help an agent understand side effects and limitations. It does not contradict the annotations; the false readOnlyHint is consistent with writing files to disk.

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 description is two sentences, front-loaded with the core operation and followed by two caveats. There is no redundant restatement of schema information and every sentence 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 moderately complex export tool, the description covers key behavioral constraints: one bridge request, midpoint frames, track selection, read-only behavior in Premiere, and no muting/visual-quality claims. The output schema covers return values. The main minor gap is explicit guidance on when to prefer this over closely related export sibling tools.

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?

All three parameters have descriptions in the input schema, so schema description coverage is 100%. The description adds top-level context like 'chosen video track' and 'midpoint,' but it does not provide additional per-parameter semantic detail beyond what the schema already includes. 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 uses a specific verb ('Export') and precisely defines the resource and scope: one file-verified composite frame at the midpoint of each clip on a chosen video track, in one bridge request. This clearly differentiates it from sibling tools like export_sequence_review_frames and export_sequence_marker_review_frames even without naming them.

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 description implies the use case of sampling clip midpoints on a selected track and highlights the 'one bridge request' efficiency, but it never explicitly states when to choose this tool over export_sequence_review_frames, export_sequence_marker_review_frames, or capture_frame. No alternatives or exclusion conditions are given, so usage guidance is only implied.

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