Wait For Video

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

Beyond annotations, the description discloses the polling interval (5s), backoff cap (15s), terminal states (done/failed/expired), timeout default (20 min), auto-download side effect, and the important non-error timeout result (still_rendering with isError=false). This is rich behavioral context that annotations alone do not provide.

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 sentences with no filler: the endpoint, polling policy, termination conditions, timeout semantics, and auto-download behavior are packed into a compact, front-loaded description. Every clause adds value.

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 3-parameter tool with a full input schema, an output schema, and annotations, the description covers the essential operational details: what is polled, how often, when it stops, what happens on timeout, and the auto-download side effect. Nothing critical for selecting or invoking the tool is missing.

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 id, download, and timeout_ms with clear meanings. The description restates the timeout default and poll behavior but does not add significant parameter-level meaning beyond what the schema provides. Baseline 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 names a specific action (poll GET /v1/videos/{id}) with a clear resource and termination condition, and distinguishes this tool from get_video_status (single status check) and download_video (explicit download) by stating it polls until done and auto-downloads. The endpoint and behavior make the tool's role unmistakable.

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 clear context: this is a blocking poll-and-wait tool that auto-downloads when finished, and timeout is a non-error retry signal. It does not explicitly name sibling alternatives or state when not to use it, but the polling and auto-download behavior strongly imply the intended use case.

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