export_fcp7_xml

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

With no annotations provided, the description carries the full burden. It does not disclose side effects (e.g., file overwriting), permission requirements, or whether the tool modifies the timeline. This leaves significant behavioral gaps.

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 sentence that immediately communicates the action and target applications. No wasted words; front-loaded with the verb 'Export' and resource 'timeline'.

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 adequate for a simple export tool with clear parameters, but it lacks information about output behavior (e.g., success/failure indication) and prerequisites. Given no output schema, the agent may need more context.

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 coverage is 100% and parameter descriptions are present. The tool description adds no additional semantic meaning beyond what is in the schema (e.g., default suffix behavior is already described). Baseline score of 3 is appropriate.

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 tool exports the timeline as FCP7 XML (XMEML) and lists specific target applications (Premiere Pro, DaVinci Resolve, Avid), which distinguishes it from sibling export tools like export_edl or export_csv.

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 compatibility with Premiere Pro, DaVinci Resolve, or Avid is needed, but does not explicitly exclude alternatives or provide when-not-to-use conditions. It gives clear context but lacks explicit exclusions.

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