Create Highlight Clip

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

Annotations show it's not read-only, not idempotent, not destructive. The description adds async processing states (queued, processing, completed, failed) and that clips are created from media files without destroying source files, which goes beyond annotations. No contradictions.

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?

Three concise sentences, each adding value: purpose, async behavior and status check, constraint and multi-segment capability. No unnecessary words.

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?

Covers async behavior, max duration, and segment stitching. With 100% schema coverage and an output schema, the description is sufficient. Could add more on merge strategy or error handling, but not critical.

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 100%, and the description adds context: max total clip duration 30 minutes, stitching multiple time ranges from different media files. This enhances understanding of how timeRanges and limits work.

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 tool creates a highlight clip from one or more media files using time ranges, distinguishing it from siblings like delete_clip, update_clip, and get_clips.

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 advises using get_clips to check async status and mentions the 30-minute max duration. It implies when to use (creating clips) but doesn't explicitly state when not to use it.

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