build_timeline

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

Discloses output files, default durations, and that out_dir is created if missing. No annotations provided, so description carries burden; lacks details on permissions, error handling, or reversal, but adequate for a non-destructive assembly tool.

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 sentences, each serving a distinct purpose: purpose/output, specific file types, assembly behavior. No wasted words, efficiently front-loaded.

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?

Covers outputs, defaults, directory creation. No output schema, so description explains return value implicitly. Could mention error behavior, but overall sufficient for the tool's complexity.

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% with descriptions for all parameters. The description adds context (e.g., 'already-downloaded', defaults for still/video) but does not substantially extend beyond schema; baseline score of 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?

Clearly states it writes a timeline from downloaded clips, specifies output formats (FCPXML, EDL, manifest), and distinguishes from siblings like build_premiere_script (script output) and place_in_resolve (direct placement).

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?

Implies usage when clips are already downloaded and a timeline is needed, but does not explicitly state when to avoid this tool or mention alternatives like build_premiere_script or place_in_resolve.

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