wan_list_resolutions

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

The description indicates a read-only operation (list, shows) and specifies the return format (table of resolutions with descriptions). Despite no annotations, it effectively communicates behavior without contradictions.

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?

Three concise sentences front-load the purpose, followed by details on content and return format. No superfluous information.

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 parameterless tool with an output schema, the description fully covers the purpose and return structure. No gaps remain.

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?

With zero parameters in the input schema, the description does not need to explain parameters. It adds value by clarifying scope ('all available') and the nature of returns.

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 resolutions for Wan video generation', specifying the verb (list) and resource (resolutions). It distinguishes from sibling tools like wan_generate_video by focusing on listing options rather than generation.

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 implies usage to retrieve resolution options but provides no explicit guidance on when to use this tool versus alternatives, such as before generating a video to select a resolution.

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