add_to_timeline

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the basic operation and does not mention mutation side effects, insert/overwrite behavior, audio-linking effects, reversibility, or whether existing timeline content can be displaced. The schema documents some parameter-level behavior, but the tool description itself remains thin.

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, front-loaded sentence with no fluff or repetition. It is concise, but it is also quite sparse for a tool with eight parameters and significant behavioral nuance, so it earns high but not maximum marks.

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?

For a complex, mutation-oriented tool with no annotations, no output schema, and several closely related siblings, the description is not complete enough. It omits mode selection, audio-linking consequences, relationship to batch/source-monitor alternatives, and expected results, so an agent would have to infer critical context from parameter docs and naming.

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 input schema already documents all eight parameters, including defaults and dependencies for source in/out points. The tool description adds no meaningful parameter semantics beyond restating that a clip goes to a track and time, leaving the schema to carry the explanatory load.

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 action ('Adds'), a resource ('media clip from the project panel'), and a destination ('to a sequence timeline at a specific track and time'). It is clear enough to distinguish from source-monitor-oriented siblings like insert_from_source and overwrite_from_source, though it does not explicitly differentiate itself from add_to_timeline_batch.

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 no guidance on when to use this tool versus alternatives such as add_to_timeline_batch, insert_from_source, or overwrite_clip. No context is given about prerequisites, preferred use cases, or excluded scenarios.

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