export_sequence

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning potential long render times, overwrite behavior, dependency on Adobe Media Encoder, or failure modes. Parameter descriptions in the schema allude to behaviors (allowOverwrite, removeOnCompletion), but the main description itself is behaviorally thin.

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 short sentences, front-loaded with the action ('Renders and exports') and purpose, with no wasted words. It is efficiently structured and easy to scan.

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?

Given the tool's complexity (10 parameters, no output schema, no annotations), this minimal description is insufficient. It fails to explain side effects, relation to other export/render queue tools (start_batch_encode, add_to_render_queue), or post-export behavior, leaving the agent with incomplete operational context.

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 100%, so the baseline is 3. The description does not add any parameter-specific meaning beyond stating the core function of rendering a sequence to a video file, which the schema already captures via sequenceId and outputPath. It does not clarify deprecated parameters or the preset resolution logic.

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 clearly states the tool's function: 'Renders and exports a sequence to a video file' and specifies its purpose as 'creating the final video.' This distinguishes it from sibling tools like export_frame (single frame), export_omf/AAF (other workflows), and export_as_project, making the purpose unmistakable.

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 phrase 'This is for creating the final video' provides clear context that this tool is intended for final video output, implicitly distinguishing it from exports of frames or intermediate formats. However, it does not explicitly name alternatives or state when not to use this tool, so it lacks full exclusion guidance.

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