hailuo_list_models

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

No annotations are provided, so the description carries full burden. It describes the tool as listing models and returning a table, implying a read-only, non-destructive operation. This is acceptable but lacks explicit statements about safety or side effects.

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 very concise with two brief paragraphs and a Returns line. It is front-loaded with the core purpose, making it easy to scan. No superfluous text.

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 no parameters, full schema coverage, and an output schema present, the description sufficiently covers the tool's purpose and output. It mentions the returns table and use cases. Could add safety hints, but overall adequate.

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 zero parameters, so there is nothing to document beyond what the schema already conveys. The description adds no parameter details, but baseline 4 is appropriate since there are no parameters.

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 'List all available models for Hailuo video generation,' identifying the verb (list) and resource (available models). It distinguishes from sibling tools like hailuo_generate_video, which focus on generation, not listing.

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 advises 'Use this to understand which model to choose for your video,' indicating it is a preliminary step before generation. It provides clear context but lacks explicit exclusions or when not to use.

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