split_clip

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

No annotations, so the description carries the full burden. It implies a destructive edit ('Blade') but says nothing about whether the clip is split into two segments, what happens to selection, whether undo is required, or what the response returns.

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?

A single efficient sentence with the action and scope front-loaded. Nothing is wasted, though it could afford one more clause of behavioral detail.

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 one-parameter tool with no annotations or output schema, the description is minimally adequate. It leaves open the post-split state (two clips vs. a cut) and any prerequisites, which an agent would want to know before invoking a destructive edit.

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 0%, so the description must compensate, and it does partially by clarifying that 'time' accepts seconds or timecode. That is meaningful format information beyond the bare string type, though no examples or constraints are given.

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?

States a specific verb ('Blade') and resource ('the primary storyline'), plus the triggering input ('at a time'). The scope constraint 'primary storyline' helps separate it from generic edit tools like trim_clip or move_clip, but no sibling is named explicitly.

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 on when to choose split_clip over alternatives like cut_ranges, keep_ranges, or trim_clip. The phrase 'at a time' weakly implies a single-point split but no conditions or exclusions are stated.

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