生成图片（异步任务）

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

No annotations are provided, so the description carries the full burden. It discloses non-blocking behavior, immediate taskId return, and that successful tasks yield public links. However, it does not mention failure scenarios, credit consumption, or rate limits, leaving significant behavioral gaps for a creation tool.

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 and front-loaded. The first sentence explains the core async behavior, the second adds follow-up actions, and the final sentence gives use cases and API endpoint. Every sentence earns its place without fluff.

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 the async complexity and lack of annotations/output schema, the description covers the essential lifecycle: create task, get taskId, query/wait, and result as public link. It lacks details on failure handling or credit implications, but these may be covered by sibling tools like get_generation_task. Overall, it is reasonably complete for an entry-point tool.

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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameter syntax and appropriately focuses on workflow rather than parameter details.

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 the tool creates an image generation task and immediately returns a taskId without blocking. This verb+resource description distinguishes it from sibling generate_image (likely synchronous) by highlighting the asynchronous nature.

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 provides clear usage context: '适合大图、批量生成' indicates when to use async mode. It also directs to get_generation_task and wait_for_generation_task for follow-up, but does not explicitly mention when to prefer the synchronous generate_image sibling.

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