export_sequence

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

No annotations exist, so the description must disclose behavioral traits. It fails to mention that Adobe Media Encoder must be installed, that exporting may be asynchronous, or that it might block until completion. The simple statement 'Export the active sequence using Adobe Media Encoder' is insufficient for a tool with significant external dependencies and side effects.

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 a single, front-loaded sentence that efficiently conveys the core purpose without redundant information. Every word contributes value.

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?

Despite moderate complexity (3 parameters, external encoder dependency), the description omits return values, side effects, and prerequisites. It does not explain what happens upon success/failure or whether the operation is synchronous, making it incomplete for an export tool.

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 schema already documents all three parameters (output_path, preset_path, work_area_only). The description adds no additional meaning beyond the parameter names mentioned in context, meeting the baseline for high coverage.

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 exports the active sequence via Adobe Media Encoder. It distinguishes from sibling tools like add_to_render_queue (which adds to queue but doesn't directly export) or encode_file (which encodes an existing file, not a sequence).

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 provides no guidance on when to use this tool versus alternatives such as add_to_render_queue or encode_file. No scenarios or exclusion criteria are mentioned, leaving the agent to infer usage context.

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