hailuo_list_actions

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

With no annotations, description discloses it returns a categorized list and serves as a reference. It is a read-only operation, and for a simple list tool, the description is sufficiently transparent.

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?

Description is 4 sentences, front-loaded with main purpose. Could be slightly more concise by merging sentences, but overall efficient.

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 simple nature, 0 parameters, and output schema present, description covers the tool's purpose adequately. No major omissions.

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?

Tool has zero parameters and schema coverage is 100%. Baseline 4 applies as description does not need to add parameter details. No param info needed.

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?

Description clearly states 'List all available Hailuo API actions and corresponding tools.' It effectively uses verb+resource and distinguishes itself from sibling tools (generation, retrieval, model listing) by focusing on listing actions and tools.

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?

Description suggests use for understanding full capabilities, but lacks explicit when-to-use or when-not-to-use guidance relative to siblings. No exclusions or alternative tool mentions.

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