export_otio

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool exports the project, implying a file-write operation, but does not disclose side effects such as whether an existing file is overwritten, whether permissions are required, or whether the operation is reversible. This is a significant gap for a tool that creates external artifacts.

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 consists of a single, front-loaded sentence with no filler words. It communicates the action, the subject, and the output format efficiently. Every word contributes to the tool's purpose, making it highly concise and well-structured.

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 simple export operation with one parameter and no output schema, the description covers the core functionality. However, it omits details like file-overwrite behavior, path requirements, and error outcomes. Given the lack of annotations and the need to fully inform an agent, the description falls short of being complete, though it is adequate for a trivial tool.

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 0%, so the description must compensate. While the tool name and description indirectly imply that output_path is the file path for the .otio output, the description does not explicitly state what the parameter represents. The meaning is inferable, but the description does not add explicit semantic value beyond the schema's type declaration.

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 states a specific verb ('Export'), a resource ('the project'), and the target format (OpenTimelineIO .otio). This clearly distinguishes it from sibling tools like import_otio (which handles the opposite direction) and save_project (which likely saves in a native format). Even without opening the schema, an agent knows exactly what this tool does and how it differs from related operations.

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 implies usage when an OTIO file needs to be produced, but it does not explicitly mention alternative tools or conditions for choosing this over save_project or export-related siblings. The context is clear enough to infer the use case, but there is no direct guidance on when not to use it or which tool to prefer in overlapping scenarios.

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