Query Video Task (Jimeng Video 3.0)

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

Annotations declare the safe read-only/idempotent profile, and the description adds substantial behavior beyond them: expected generation latency of 1-3 minutes, the full status enumeration, polling guidance, and critically the 1-hour expiry of the returned video URL. This is exactly the extra operational context annotations cannot express.

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?

Front-loaded with purpose, then structured Args/Returns/polling guidance. Slightly redundant in stating the 1-hour URL expiry twice (in Returns and the closing Important line), but every block carries useful information.

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?

With no output schema, the description takes on the burden of documenting return values and does so fully: status values, video_url presence condition, and expiry. Latency expectation and polling behavior round out what an agent needs to call and use this 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% for the single task_id parameter, so the baseline is 3; the description adds provenance by stating the ID is what jimeng_generate_video returned, which helps the agent source the value correctly.

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?

States a specific verb (query) and resource (status and result of a Jimeng Video 3.0 task), and explicitly ties itself to the sibling tool jimeng_generate_video as its prerequisite, so an agent can distinguish it from the generation tools 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?

"Use after calling jimeng_generate_video" gives clear triggering context, and the polling advice for in_queue/generating statuses tells the agent how to act on results. It does not mention jimeng_generate_video_and_wait as the blocking alternative, which would be the natural way to avoid polling entirely.

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