hailuo_get_task

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns status and result, lists possible states (pending, completed, failed), and mentions retrieving video URLs. It does not describe side effects or permissions, but as a query tool, the behavioral traits are clear.

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 with a clear structure: a one-sentence summary, a bulleted 'Use this when' list, a section on task states, and a returns line. Every sentence is necessary and well-organized.

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?

Given that an output schema exists (context signals indicate 'Has output schema: true'), the description adequately covers return values by mentioning 'Task status and generated video information including URLs and status.' The task states list provides additional context.

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 input schema has 100% description coverage, so baseline is 3. The description does not add extra meaning beyond the schema, which already explains that task_id is from generation tools. No further parameter context is provided.

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 'Query the status and result of a video generation task,' which is a specific verb and resource. It distinguishes from siblings like 'hailuo_get_tasks_batch' by focusing on a single task, and from generation tools by being a query operation.

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 lists when to use the tool: 'check if generation completed,' 'retrieve video URLs,' 'get full details.' It also describes task states. However, it does not explicitly exclude cases where alternatives like 'hailuo_get_tasks_batch' might be better.

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