h3_art_generate

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the task is paid and requires specific auth/environment configuration, but it does not say whether the call starts an asynchronous job, returns a job ID, blocks, or must be followed by h3_art_job_status.

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 a single front-loaded sentence with no wasted language. Every clause contributes a useful qualifier: paid, managed, single task, and required environment/auth settings.

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 paid generation tool with no annotations, no output schema, and four undocumented parameters, the description is too sparse. It covers task type and environment requirements but omits parameter meanings, job lifecycle/polling behavior, and sibling routing.

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%, so the description must explain all four parameters, but it only implies 'prompt' via 'text-to-video'. It says nothing about seed, duration, or resolution, including the unusual default value '480p横'.

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?

It uses a specific verb, 'Submit', and a specific resource, 'one paid managed H3 text-to-video task'. The 'paid managed' qualifiers help distinguish it from the bare h3_generate sibling, but it does not explicitly name alternatives such as h3_art_generate_workflow or h3_art_quote.

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 states prerequisites (AUTODL_ART_TOKEN and H3_ART_ENABLE_PAID=1), which is useful context. However, it gives no guidance on when to choose this tool over h3_art_generate_workflow, h3_art_quote, or h3_generate, and no when-not conditions.

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