add_to_timeline

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

No annotations are provided, so the description carries full burden. It implies a write operation ('adds') but doesn't disclose behavioral traits such as whether it requires specific permissions, if it's destructive (e.g., overwriting content), or how errors are handled. The mention of 'insertMode' hints at behavior, but details are lacking.

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 a single, efficient sentence that front-loads the core action and key details (media clip, project panel, sequence timeline, track, time). There's no wasted verbiage, making it easy to parse quickly.

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 no annotations and no output schema, the description is moderately complete for a tool with 5 parameters. It covers the basic purpose but lacks details on usage context, behavioral implications, or return values. For a mutation tool, this leaves gaps in understanding full operation.

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 documents all parameters. The description adds minimal value beyond the schema by implying the tool's purpose, but doesn't provide additional context like parameter interactions or examples. Baseline 3 is appropriate as the schema handles most documentation.

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 ('adds'), the resource ('media clip from the project panel'), and the destination ('to a sequence timeline at a specific track and time'). It distinguishes from siblings like 'move_clip' or 'remove_from_timeline' by specifying addition rather than movement or deletion.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites like needing an existing sequence or project item, or when to choose 'insertMode' options. Siblings like 'move_clip' or 'trim_clip' serve different purposes, but this isn't clarified.

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