export_omf

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'export omf.' It does not state whether a file is written to disk, what path is used, whether the active sequence is exported, whether existing files are overwritten, or what side effects occur. This is even less informative than a typical minimal export description.

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 short but not meaningfully concise; it omits necessary detail while including the filler phrase 'expanded operation.' This is under-specification rather than efficient conciseness, and the only substantive content is a restatement of the tool name.

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 no annotations, no output schema, and no documented parameters, the description should at least clarify what the export acts on (e.g., current sequence) and what the result is (e.g., file path or success status). It provides only the format name, leaving essential operational context 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?

The schema has zero documented parameters and 100% coverage (vacuously), so the baseline is 4. The description adds no parameter-level meaning, but there are no parameters for it to explain. The schema's additionalProperties=true is not addressed, but the zero-parameter baseline still applies.

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 restates the tool name ('export omf') without adding meaningful scope or object. 'Premiere Pro expanded operation' is generic boilerplate and does not clarify what is exported (e.g., active sequence, media, project), destination, or format specifics. It cannot be distinguished from siblings like export_aaf or export_as_fcp_xml beyond the literal format name.

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?

There is no guidance on when to use export_omf versus export_aaf, export_as_fcp_xml, or export_sequence. No prerequisites, context, or exclusions are provided, so the agent must guess whether this is the correct export tool for a given task.

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