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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description carries the rest. It never mentions that generation is a long-running/async operation whose result must be fetched (a nexscope_media_task_result sibling exists), nor cost, rate limits, or failure behavior. The one 'videoType must not be supplied' note refers to a parameter absent from the schema, which adds confusion rather than clarity.

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?

Two sentences, front-loaded with the capability and the input modes, no filler. The second sentence is a useful guardrail even if it references a field not in the schema.

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?

A 10-parameter, mutating generation tool with no output schema needs the description to say what comes back (task id? URL?) and how to retrieve it. It says nothing about the return path, pricing, or expected latency, so an agent cannot close the loop after calling it.

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 100%, so the schema already documents duration, resolution, aspect ratio, prompt limits, and the conflictsWith constraints among image/video/lastFrame inputs. The description reinforces the mutually exclusive input modes but adds no format or semantic detail beyond 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?

States a specific verb and resource ('Generate a ... video') and enumerates the three input modes (primary image, up to 9 reference images, or reference video). The qualifier 'faster' implicitly separates it from nexscope_seedance_2_0_video_generation, but the sibling relation (quality vs. speed tradeoff) is never stated explicitly.

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 only guidance is the negative constraint that videoType must not be supplied. There is no statement of when to choose this over nexscope_seedance_2_0_video_generation, nexscope_seedance_2_0_mini_video_generation, or nexscope_seedance_2_5_video_generation, which are the obvious alternatives given the sibling list.

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