seedance_list_resolutions

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature or side effects. For a list tool, it is likely safe, but the description fails to confirm this, leaving the agent without explicit behavioral context.

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 two sentences plus a returns line. It is front-loaded and to the point. However, the claim 'with use cases' is not fully backed by the description text, slightly reducing conciseness effectiveness.

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 is fairly complete. It states what is returned: 'Tables of resolutions and aspect ratios with descriptions.' This provides enough context for an agent to understand the tool's output without needing additional details.

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, and schema coverage is 100% trivial. Per guidelines, baseline is 3. The description adds no parameter information because there are none, but it also does not add extra context about the parameters that could be helpful.

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 what the tool does: 'List all available resolutions and aspect ratios for Seedance.' It uses specific verbs and resources, and it distinguishes itself from sibling tools like seedance_generate_video and seedance_list_models by focusing on resolution and aspect ratio options.

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 context by mentioning 'use cases' but does not explicitly state when to use this tool versus alternatives or provide prerequisites. Since it's a simple list tool, the usage is somewhat self-evident, but no detailed guidance is given.

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