mm_query_video_task

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

The description discloses important side effects (downloading MP4 to local) and return behavior for both in-progress and success states, going beyond what annotations alone provide. It also mentions a default output path, adding useful context.

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 concise and well-structured, starting with a clear summary followed by Args and Returns sections. Every sentence serves a purpose without redundancy.

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 2-parameter tool, the description covers the essentials: purpose, parameter semantics, and return value behavior. It lacks detailed error handling or explicit alternative exclusions, but the provided info is sufficient for normal agent use.

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?

Despite 0% schema coverage, the description explains both parameters thoroughly: task_id comes from mm_generate_video control flow, and output_path has a default with optional saving. This fully compensates for the bare input 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 clearly states the tool queries a video generation task and downloads the MP4 file after success, using a task ID from mm_generate_video. This specificity differentiates it from siblings like mm_query_comic_video.

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 explicitly ties task_id to mm_generate_video, giving clear context on when to use this tool. It doesn't explicitly exclude alternatives, but the source of the task ID and the tool's name make its purpose clear enough for an agent.

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