Export Omf

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the format and domain context; it does not disclose what happens if output_path already exists (overwrite vs fail), whether the active sequence is a precondition, or any size/permission constraints for a not-idempotent write.

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?

A single sentence that leads with the action and resource and ends with just enough format context. Nothing is padded and nothing essential is buried.

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?

An output schema exists, so return values need not be described, and the 8-parameter schema is fully documented. Still, for a non-idempotent export operation the description says nothing about preconditions (an active sequence) or how an existing file at output_path is handled, leaving a behavioral gap an agent must guess at.

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% for all 8 parameters, including defaults and the 0=AIFF/1=WAV encoding, so the schema already carries the parameter semantics. The description supplies no additional parameter meaning, which is consistent with the baseline 3 when the schema does the heavy lifting.

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?

Names a specific verb (export) and resource (the active sequence) plus the output format, and expands the OMF acronym with domain context ('audio post-production'). It is distinguishable from generic siblings like export_sequence, but it never contrasts itself with the closely related export_aaf or export_as_fcp_xml, so sibling differentiation is implicit rather than stated.

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 'for audio post-production' implies the scenario in which OMF is the right interchange format, which is useful nudging. However, there is no explicit when-to-use/when-not guidance and no pointer to export_aaf or export_as_fcp_xml as the alternative for other post workflows.

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