Add To Timeline Batch

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

The description discloses meaningful behavior beyond the annotations: preflighting before first insertion, read-back verification of every placement, and fail-closed behavior if Premiere cannot verify one. This gives the agent a clear model of how the tool behaves at execution time.

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 concise, front-loaded sentences covering purpose, limits, and failure behavior. It avoids filler and appropriately leaves parameter-level detail to the schema.

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?

With full schema coverage, an output schema present, and annotations covering safety hints, the description provides the missing operational context: batch limit, preflight, read-back, and fail-closed behavior. No critical call-time decision is left unaddressed.

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 100%, so the schema already explains the individual parameters. The main description adds the undocumented 32-item limit and validation semantics, while the clips schema adds ordering and insert-edit constraints, providing extra value beyond the raw 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 states a specific verb ('Insert'), a specific resource ('project items'), and a clear scope ('up to 32 in one validated CEP request'). The 'batch' framing and the 32-item limit clearly distinguish it from the singular sibling add_to_timeline.

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 and clips schema point to add_to_timeline semantics, and 'up to 32' implies a multi-item batching use case. However, it never explicitly states when to choose this tool over add_to_timeline or what conditions would make the singular tool preferable.

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