Download media clip

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

Annotations already establish that this is a non-read-only, non-destructive operation. The description adds that output is saved locally and that authorization is involved, which is useful, but it does not explain what happens when confirm_authorized is false or whether the download is a file saved to disk versus streamed. It adds some context without contradicting annotations.

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 carry the core purpose, output formats, local saving, and timestamp syntax. There is no filler, and the most important constraint ('precise authorized time range') is front-loaded.

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 six parameters and no output schema, the description plus the schema and annotations cover the essential details: purpose, format choices, timestamp formats, and authorization flag. The main omission is explicit guidance on choosing download_clip over download_media, but this is a minor gap given the strong schema coverage.

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 all six parameters. The description's mention of timestamp formats and MP4/MP3 output is helpful but largely repeats what the schema already states, so the baseline of 3 applies.

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 states a specific verb and resource: 'Download only a precise authorized time range locally as MP4 video or MP3 audio.' The 'only ... time range' wording differentiates it from the sibling download_media, which implies full-media downloads, so an agent can tell them apart without opening the schema.

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 this tool is for extracting a specific time range rather than downloading entire media, but it never explicitly says when to prefer download_clip over download_media or inspect_media. The context is clear enough to infer the primary use case, but no exclusions or alternatives are named.

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