list_video_models

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

The tool has no annotations, and the description does not disclose any behavioral traits such as side effects, permissions required, or rate limits. It is presumably a safe read-only operation, but this is not explicitly stated.

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 extremely short and front-loaded, fitting in a single sentence. While concise, it borders on too minimal, but it still effectively communicates the core action.

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 and an existing output schema, the description does not need to explain return values. However, it fails to provide context about the relationship to sibling tools or what the output represents, leaving room for improvement.

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 tool has zero parameters, so the description need not add parameter meaning. The schema covers all parameters, meeting the baseline score of 4 as specified.

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 lists the 'single enabled HunyuanVideo generation profile', which distinguishes it from sibling tools like 'list_uploaded_video_inputs' and 'estimate_video_job'. However, it does not explain what a 'generation profile' is, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, conditions, or context for invocation.

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