slip_clip

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the core mutation and its non-effects, plus the sign convention for offset, but it omits permissions, reversibility/undo behavior, source-boundary handling, linked-clip effects, and what the operation 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?

It is a single, front-loaded sentence with no wasted words. The parenthetical sign convention is compact and directly useful.

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 four-required-parameter mutation tool whose schema fully documents the parameters, the description supplies the essential conceptual model and offset sign. It lacks edge-case and result-behavior details, but it is sufficient for correct selection and invocation.

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 baseline is 3, but the description adds meaning beyond the schema's bare 'Seconds' for offset: positive means later in the source and the offset is source-relative rather than a timeline move. It does not add further meaning for the track and clip index parameters, which the schema already documents well.

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 the specific edit operation (slip), its effect (show a different part of the source), and the key invariant (without moving or resizing the clip). This distinguishes it from move, trim, and slide-style edits that alter timeline placement or duration.

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?

It gives a clear context for use: change which source segment is shown while preserving the clip's timeline position and size. The exclusion of moving/resizing is useful, though it does not explicitly name alternative sibling tools such as slide_clip or trim_clip.

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