export_fcp7_xml

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Export timeline' without mentioning side effects (e.g., whether the timeline is modified, if file creation is atomic, or what happens on error). Minimal information is given, which is insufficient for a write operation.

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 a single, concise sentence of 12 words that front-loads the core purpose. Every word contributes meaning; there is no fluff or redundancy. It effectively communicates the tool's function in minimal space.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations) and presence of sibling export tools, the description is adequate but lacks context like what XMEML is or how the 'timeline' is referenced (via filepath). It could be slightly more helpful, but for a straightforward export tool, it covers the essentials.

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 input schema has 100% parameter descriptions, so the baseline is 3. The description adds no extra meaning beyond the schema, such as example values, format constraints, or relationship between parameters. No additional guidance is provided for the agent.

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 clearly states the verb 'Export', the resource 'timeline as FCP7 XML', and the purpose 'for Premiere Pro, DaVinci Resolve, and Avid compatibility'. It directly distinguishes from siblings like export_csv and export_edl by specifying the target format and purpose.

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 for exporting to FCP7 XML for compatibility but provides no explicit guidance on when to use this tool versus sibling export tools (export_csv, export_edl, export_resolve_xml). No prerequisites or scenarios are mentioned, leaving the agent to infer usage from the name alone.

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