seedance_create_video

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning asynchronous behavior, return type, authentication, or side effects, leaving the agent uncertain about what to expect.

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 short but under-specified; it provides no useful information beyond a basic purpose. The single sentence does not earn its place because it simply restates the tool's name in a slightly longer form without adding actionable details.

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?

With 11 parameters and no annotations, the description is grossly incomplete. It does not explain how to construct a request, what the output represents, or the relationship between this tool and the sibling tools. An output schema exists, but the description lacks critical context for execution.

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?

Schema description coverage is 0% and the description mentions no parameters. The 11 parameters are entirely unexplained, so the agent cannot know what values to provide beyond the prompt being required by the schema.

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 uses a specific verb ('Create') and resource ('Seedance video generation'), making the tool's primary function clear. It is distinguishable from sibling tools that focus on model guidance, status retrieval, and completion waiting, though it does not explicitly contrast them.

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 the sibling tools, no prerequisites are mentioned, and there is no context about required parameters beyond the schema. The description offers no 'when' or 'when not' usage instructions.

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