Place clip on timeline

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

With no annotations, the description carries full burden. It discloses key behaviors: automatic file import, optional trimming, mode effects (overwrite vs ripple), and automatic audio routing. It omits error conditions, undo behavior, or prerequisites like project/sequence requirements.

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 two sentences, front-loaded with the core action, and free of fluff. Every sentence adds value.

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 covers purpose, parameters, and modes, but lacks information on return values (e.g., success/failure), error handling, or prerequisites (e.g., active project/sequence). For a 6-parameter tool with no output schema and no annotations, this is a noticeable gap.

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%, but the description adds value beyond the schema by explaining importing behavior for mediaPath, clarifying trim parameters with 'source in/out-point', and detailing mode effects. This adds meaningful context.

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 action ('Place a media clip on a video track at a given time') using a specific verb and resource. It adds details about importing, trimming, and modes, distinguishing it from sibling tools like premiere_import_files.

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 explains the two modes (overwrite vs insert) and their effects, providing context for when to choose each. However, it does not explicitly state when not to use this tool or mention alternatives (e.g., using add_title for different clip types).

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