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

Beyond the readOnly annotations, it discloses the status states, that after_steps include prices in credits, and that download_url is regenerated per answer with an expiry window. It also states the operation is free and explains how to get a new link later.

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?

It front-loads the status-checking purpose, then covers only materially useful details: statuses, after_steps pricing, link expiry, re-call behavior, and cost. There is no filler.

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?

No output schema exists, but the description explains the status values and key returned fields such as after_steps, download_url, and download_expires_in_seconds. That is enough for an agent to call and interpret 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 coverage is 100%, and the id field already documents that it comes from make_video. The description reinforces the source but adds no syntax or format details beyond the schema.

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 specifies that this retrieves the status of a video produced by make_video or a subsequent step, enumerating the possible states and post-ready artifacts. It clearly implies a singular lookup by id, but it does not explicitly distinguish this tool from list_videos.

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 tells the agent to call this after make_video and to call again for a later download link, giving clear usage context. It does not name explicit when-not conditions or alternatives such as list_videos.

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