import_fcp_xml

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

With no annotations, the description carries the full burden. It discloses that Premiere creates a new sequence, that UI suppression is requested, and that malformed/unsupported XML can be rejected. This is more transparent than average, though it omits details like undo behavior and return values.

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?

Three concise sentences with zero waste: purpose, outcome, and critical warning/guidance. Every sentence earns its place, and it's front-loaded with the main function.

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 only one parameter and no output schema, the description covers the essential context: what gets created (new sequence), the expected input format, and a key failure mode. It could mention if the import is additive to the current project or how success/error is reported, but it's quite complete for a single-param 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?

The input schema property description fully covers the filePath parameter (absolute path, .xml extension), so schema coverage is 100%. The description adds no new parameter-level meaning beyond identifying the file type as FCP7 XML, which is already implied by the tool's purpose. Baseline 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 imports a Final Cut Pro 7 XML (XMEML) file into the current project, specifying the exact resource and action. It distinguishes from siblings by explicitly noting it's for FCP7 XML, not modern FCPXML from FCP X, setting it apart from import_edl and import_sequences.

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?

It provides clear usage context: import legacy FCP7 XML files, not FCPXML 1.x. This is an explicit when-to-use and when-not-to-use guideline. However, it doesn't name alternative tools like import_edl or import_media, so it stops short of the 'alternatives' level.

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