split_clip

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

With no annotations, the description carries the transparency burden. It adds useful details: the operation applies to 'every clip on a track' and returns 'the new clip count' for confirmation. It does not mention side effects like undo or edge cases, but the provided context goes beyond the bare name.

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 two sentences with no filler. It front-loads the action and adds a brief note on the return value, making it maximally concise.

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?

The description explains what the tool does, its scope, and the return value, which is adequate given no output schema and a moderate number of parameters. It lacks edge-case handling but is otherwise complete for the tool's purpose.

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?

The schema covers 67% of parameters with descriptions (track_index and time_seconds), and track_type has an enum/default that clarifies its meaning. The tool description does not add further parameter-specific information, so it does not exceed the schema's coverage.

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 'Cut every clip on a track at the given time' which is a specific verb+resource. It also distinguishes from sibling tools like trim_clip or remove_clip by clarifying it is a split operation equivalent to the razor tool.

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 an analogy to the razor tool but does not explicitly state when to use this tool versus alternatives like trim_clip or remove_clip. There is no mention of exclusions or preferred scenarios.

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