build_premiere_script

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (generates a script that appends clips to the active sequence) and that the script file is written to out_dir. However, it does not mention potential error conditions (e.g., if no sequence is open) or side effects beyond timeline modification.

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 consists of three efficient sentences: purpose, usage, and identity. Every sentence adds unique value, and there is no redundancy or filler.

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 low complexity (2 parameters, no output schema, no annotations), the description covers all essential aspects: what it does, how to use it, prerequisites, and the output file. No gaps are evident.

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%, so the schema already documents both parameters. The description adds value by explaining that clips are 'chosen' and appended in order, and that out_dir is created if missing. It also clarifies the default duration for stills (5 seconds).

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 uses a specific verb ('generate') and resource ('Premiere Pro script'), and clearly states the action ('imports the chosen clips and appends them to your ACTIVE sequence'). It distinguishes from siblings by calling it 'the direct-to-timeline path for Premiere'.

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 provides explicit context on when to use the tool ('Run it in Premiere via File > Scripts... with a project + sequence open') and implicitly contrasts with sibling tools (e.g., place_in_resolve). It does not explicitly state when not to use it, but the guidance is clear.

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