Get video

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

With no annotations provided, the description carries the burden. It discloses the core behavior (download to disk, returns file path) and the completion requirement. However, it does not mention error behavior if called too early, file overwrite rules, or directory creation. For a simple download tool, this is acceptable but not rich.

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 short, front-loaded sentences with no redundant phrases. Directly states the action, return value, and precondition.

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 simple download tool with only two parameters and no output schema, the description covers the essential purpose, return value, and prerequisite. It lacks some edge-case details but is sufficient for an agent to select and invoke correctly, especially with the schema providing param semantics.

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%, with both parameters documented (output directory with default, requestId from generate_video). The description adds no additional parameter details; the schema already provides semantic meaning.

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 a specific action ('Download a completed Grok video generation to disk') and identifies the resource. It distinguishes get_video from sibling tools: generate_video creates, get_generation likely fetches status, while get_video downloads the actual file.

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?

It states a clear precondition ('Requires the generation to be COMPLETED'), implying it should be used after generation finishes. However, it does not explicitly name alternatives or state when not to use it, so it's not as direct as a tool that says 'use generate_video to create, get_video to download'.

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