clip_export

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

With no annotations, the description carries the burden. It discloses a key behavioral trait: 'Downloads only the requested segment — not the full video.' It also mentions broad site support. However, it does not describe potential side effects like network usage, file format, or failure modes, and it lacks any detail about authentication or rate limits.

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 three concise sentences, each adding value. It leads with the action, clarifies behavioral scope, gives a use case, and states supported sites. No redundant wording.

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 tool with 5 params and no output schema, the description covers purpose, key behavior, use case, and platform support. It doesn't explain return values or output file specifics, but those are partly covered by parameter descriptions. Given the sibling context, this is adequately complete for an agent to select and invoke the tool correctly.

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% with all parameters already documented. The description adds minimal extra semantics beyond the schema, such as 'specific time range' which maps to start/end, but does not provide syntax or format details beyond what the schema already contains. Baseline of 3 is appropriate.

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's function: 'Export a video clip from a URL for a specific time range.' It also differentiates from siblings by emphasizing that it downloads only the requested segment, not the full video, which is distinct from audio-focused tools like download_audio or transcribe_audio.

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 implies when to use it: 'Perfect for extracting moments around keyword matches.' However, it does not explicitly mention when not to use it or contrast with alternative tools like download_audio or highlights. The use case is clear but not exhaustive.

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