Trim video

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

No annotations are provided, so the description carries the full burden for behavioral transparency. It does not disclose whether the tool creates a new file, what the default output behavior is, or that re-encoding vs stream copy affects accuracy. It does add context about time formats, but that is more parameter semantics than behavioral disclosure.

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 just two sentences, front-loaded with the core purpose and containing zero filler. Every sentence adds useful information about usage and time formats.

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 covers the main usage pattern for trimming, but it omits that the start parameter is optional (defaults to beginning of file per schema), and it does not mention the default output_path behavior. With six parameters and no output schema, these gaps make it slightly incomplete for a broader understanding.

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 provides full descriptions for all six parameters (100% coverage), so the baseline is 3. The description adds meaningful value by explaining that times can be seconds (12.5) or clock form (1:23:45.6) and by clarifying the rule for omitting both end and duration. This goes beyond the schema's individual parameter descriptions.

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 uses the specific verb 'Cut' with the resource 'video' and clearly defines the scope as 'a time range', distinguishing it from siblings like crop_video (spatial cropping) and concat_videos (joining videos). It is immediately clear what the tool does.

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 gives explicit instructions on how to specify parameters: provide a start time plus either an end time or duration, and that omitting both keeps everything from start to file end. It also explains accepted time formats. However, it does not mention when to use this tool over alternatives, such as when to prefer fast_copy for quick cuts versus re-encoding for precision.

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