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

Annotations declare readOnlyHint=true, which is consistent since this only produces a downloadable file. The description goes well beyond by disclosing what each format drops (transitions/audio in otio/edl, dropped dissolves when clips lack handles), the zero cost, the return payload location (`inhalt`), and the relink workflow. No contradiction with annotations.

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?

Front-loaded with purpose, costs, then per-format breakdown and the final write-to-disk instruction. Dense but every line carries operational detail; the per-format paragraphs are warranted but make it long for a 2-param tool.

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?

No output schema exists, so the description correctly explains what the response contains (`inhalt` holding the whole file plus a filename) and instructs the agent to write it to disk. Combined with format semantics and relink steps, nothing needed to call it correctly 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 the enum already documents format choice, so baseline is 3; the description adds real value by explaining the exact fcpxml internals (V1 storyline with gaps, centered cross dissolves dropped at headless clips, V2+ as connected clips), otio contents (no audio/transitions), and edl channel limits, extending beyond the schema's one-line summaries.

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?

States a specific verb (export) and resource (one sequence as an NLE editing file), names exactly what formats produce what, and is clearly distinguishable from siblings like lab_start_export or lab_export_profiles by naming the NLE/interchange use case.

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 format enum guidance in the schema and the description's per-format notes effectively tell the agent when to pick fcpxml vs otio vs edl. It doesn't explicitly say when NOT to use this tool (e.g. vs a render export), but for the interchange purpose the routing is clear.

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