export_sequence_as_project

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

With no annotations, the description carries the full burden. It does usefully disclose that media is referenced rather than copied, but omits whether an existing file at the target path is overwritten, whether the current project is modified, and what happens if no sequence is active.

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?

One front-loaded sentence with zero filler, but at that length it leaves no room for the prerequisite and overwrite details an agent would need.

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 and no annotations, so the description must cover return value, side effects, and path constraints itself. It does not: nothing is said about what is returned, whether media is consolidated, or how failures (missing active sequence, invalid path) surface.

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% and the single outputPath parameter is never mentioned in the description. The implied .prproj extension is the only hint about the value; there is no guidance on absolute vs. relative paths, directory existence, or overwrite behavior.

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 (save/export) applied to a named resource (the active sequence) and a named output format (.prproj), which separates it from save_project, save_project_as, export_sequence, export_fcp_xml, and export_aaf. It does not explicitly name those siblings, so it falls short of a 5.

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 never says when to choose this over save_project_as (whole project) or export_sequence (media render), nor does it state prerequisites such as an active sequence being open. Usage is only inferred from the phrase 'as a separate .prproj'.

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