Get Video Result

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the precondition and the failure behavior when called too early. It does not discuss return format or side effects, but for a read-only retrieval tool this covers the most important non-obvious behavior.

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 two crisp sentences with no filler. The core purpose is front-loaded, and the critical usage caveat follows immediately. Every sentence earns its place.

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 single-parameter tool with an output schema, the description covers the essential context: what it returns, when it is valid, and what happens if used prematurely. Sibling tools are available as context, and no additional prerequisities or side effects are needed for correct invocation.

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 already provides 100% coverage for job_id, including its source ('Identifier returned by create_video'). The description adds no new parameter-level meaning beyond tying the job to a completed video, which is implicit in the tool's purpose. Baseline of 3 is appropriate given the schema's thoroughness.

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 ('Retrieve') and resource ('finished video for a completed job'), making the tool's function unambiguous. It also implies the distinction from get_video_status by focusing on the result rather than status. An agent can clearly tell this tool's purpose without looking at 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 gives an explicit precondition: only use after get_video_status reports 'completed'. It even warns that calling earlier is an error, not a wait, which prevents misuse. This is strong, actionable guidance for when to use the tool.

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