export_omf

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

With no annotations and a vague description, there is no disclosure of side effects, permissions required, or potential impacts on the project. The operation's behavior remains completely opaque.

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 extremely brief, but its brevity is not effective because it omits essential details. It is under-specified to the point of uselessness, rather than being a well-structured concise summary.

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?

The description is critically incomplete for an export operation. It lacks information about output format, file handling, sequence requirements, or any relevant constraints, making it impossible for an agent to use this tool effectively.

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?

Although the schema has no parameters (100% coverage trivially), the description adds no meaning beyond the schema. It fails to clarify what the operation does or what inputs would be expected, leaving the empty parameter list meaningless.

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 'Premiere Pro expanded operation: export omf.' merely restates the tool name without explaining what exporting OMF entails, its purpose, or its effect. It is a tautology that provides no actionable information.

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 gives no indication of when to use this operation versus alternatives like export_sequence or export_aaf. No context is provided regarding prerequisites, typical scenarios, or distinguishing features.

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