export_as_project

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

No annotations are provided, so the description must carry the full behavioral burden. It fails to disclose that this operation writes a project file, any side effects, output location, or cancellation behavior. The word 'export' only implies a write operation without specifics.

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 under-specified. It is a near-verbatim restatement of the tool name and the phrase 'expanded operation' adds no meaningful information, so it fails as concise specification.

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?

This is a complex export operation with no annotations and no output schema, yet the description explains nothing about the result, input requirements, or relationship to sibling export tools. It is completely inadequate for safe invocation.

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 tool has zero defined parameters and the schema coverage is high, so there is little for the description to add. The baseline of 4 applies because no parameter explanation is necessary, though 'expanded operation' hints at potential hidden options without documenting them.

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 'export as project' merely restates the tool name and adds the vague phrase 'expanded operation.' It does not specify the export format, scope, or how it differs from sibling tools like export_as_fcp_xml, export_omf, or export_sequence.

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 this tool versus alternatives. The description provides no context, prerequisites, or exclusionary criteria, leaving the agent without direction for tool selection.

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