export_sequence

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

With no annotations provided, the description carries the full transparency burden but only states the core purpose. It fails to mention the dominant behavioral trait—that .epr presets control codec/quality/resolution—or any side effects/requirements of the render pipeline, which is a significant disclosure gap for a 10-parameter tool.

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 short sentences, front-loaded with the action verb. The only blemish is that "This is for creating the final video" largely restates "exports a sequence to a video file," a minor redundancy, but overall it remains tight.

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 complex tool with 10 parameters, no output schema, and many sibling export/encode/render tools, two sentences are insufficient. The description omits crucial context about preset resolution, blocking/long-running behavior, and how it relates to encode_project_item or add_to_render_queue, leaving the rich sibling list's distinctions unaddressed.

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?

With 100% schema description coverage, the baseline of 3 applies; the rich param docs in the schema handle semantics. The description adds no param-level meaning (and doesn't need to given the schema's thorough coverage of presets, deprecations, and overwrite behavior).

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?

"Renders and exports a sequence to a video file" provides a specific verb plus resource, and "creating the final video" implies finished output vs. the interchange/frame exports (export_as_fcp_xml, export_frame) among siblings. It's clear and differentiated at a high level, though it never explicitly names a sibling like encode_project_item to contrast against.

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?

"This is for creating the final video" implies intended use and subtly distinguishes from frame/XML exports, but there's no explicit guidance on when not to use this tool or which sibling to prefer (e.g., add_to_render_queue, encode_file). The usage context is only implied through the purpose statement, not explicit.

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