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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds nothing about the cost, latency, or asynchronous/task-based nature implied by the sibling nexscope_media_task_result, nor what happens to the generated asset. For a generative, non-read-only, open-world call this is a substantial disclosure gap.

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?

A single front-loaded sentence with no filler. It is efficient, though the terseness leaves little room for the routing or behavioral detail an agent needs.

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 no output schema, seven parameters, four enums, model-dependent constraints across five video models, and an obviously asynchronous generation workflow, the description should explain what is returned (e.g., a task identifier) and how to retrieve the result. None of that is present.

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% and the per-parameter descriptions, enums, and x-nexscope-constraints already document model-dependent limits on imageList size, videoTime, and resolution. The description only gestures at 'prompt and product image references' and adds no meaning beyond the schema, so baseline 3 applies.

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 names a specific verb and artifact ('Create a product-selling video') plus its two main inputs (prompt, product image references), which is clearer than a bare restatement of the name. It does not, however, distinguish this tool from the many sibling video-generation tools (seedance_*, happy_horse_2, kling_*, wan_*) that also take a prompt and images.

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?

There is no guidance on when to use this tool versus the underlying model-specific generators it wraps (nexscope_seedance_2_0_video_generation, nexscope_happy_horse_2_video_generation, etc.), nor on prerequisites such as public image URLs or expected downstream polling. The agent must infer usage entirely from the schema.

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