clip

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

With no annotations, the description carries the behavioral burden and usefully discloses that clip re-encodes rather than stream-copies, and that it produces separate output files. It could add more about the performance cost of re-encoding, but the core behavioral distinction is clearly stated.

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?

Two tight sentences with no wasted language. The purpose is front-loaded and the sibling comparison follows immediately, making it easy to scan.

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 a fully described schema and no output schema, the description provides enough context to select and call the tool correctly. It omits some file-output details such as where multi-segment output lands, but those are covered in the schema.

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 input, output, segments, start/end times, and overwrite semantics. The description reinforces the notion of one or more segments and exact times, but adds no parameter details beyond what the schema provides.

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 and resource: extracting frame-accurate sub-segments into separate files. It also explicitly distinguishes itself from trim, making the tool's role clear without needing to inspect schemas.

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?

Directly names the relevant alternative, trim, and explains the selection condition: trim is a fast stream copy that snaps to a keyframe, while clip re-encodes for exact cuts. This gives an agent clear guidance on when to choose clip over trim.

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