Generate Premiere XML

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

No annotations are provided, so the description carries full burden. It discloses file creation and return of XML but omits important traits like overwrite behavior, permission needs, or the max clip limit of 200 evident in the schema.

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 highly concise: two sentences plus an import instruction. Every sentence adds value (generation, output, return, import), with no redundancy or fluff.

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?

For a tool generating XML from clips, the description lacks details on file overwrite, supported codecs, error handling, and the 200-clip limit from schema. No output schema, but the import instruction is helpful. Adequate but with gaps.

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 moderate (4 of 6 parameters have descriptions). The description adds no extra meaning beyond the schema; it mentions 'editing decisions' referencing the clips parameter but does not explain width/height or fps defaults beyond schema.

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 it generates a Premiere/FCP XML file from a list of editing decisions, specifying the output file saving and import instruction. It differentiates from sibling tools like decupar or catalog_brolls by focusing on XML generation.

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 editing decisions are available but does not explicitly state when to use vs alternatives, such as decupar for creating the decision list. No when-not-to-use or alternative guidance is provided.

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