生成图像

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

With no annotations, the description bears full burden. It discloses core behavior: submitting a task, waiting up to 60s, short tasks return URL, long tasks return task_id. It also explains the inline_image parameter behavior and the effect of wait_seconds. Minor omission: no mention of error handling or cost implications, but sufficient.

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: three sentences, front-loaded with purpose, then prerequisite, then behavior. No redundancy or unnecessary information. Every sentence earns its place.

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 no output schema and 4 parameters with nested objects, the description explains async behavior, prerequisites, and follow-up (get_task). It covers the return values (URL or task_id) adequately. Could mention URL expiry, but not essential. Complete enough for common use.

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 baseline is 3. The description reinforces the guidance to use describe_model for params format, but does not add significant new meaning beyond the schema. The schema already describes each parameter adequately.

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 '提交图像生成/编辑任务' (submit image generation/editing task), specifying the verb (submit/generate/edit) and resource (image). It distinguishes from sibling tools like generate_audio and generate_video by focusing on 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?

The description advises to first use describe_model to confirm model parameters, and explains the default wait behavior with short vs long tasks, explicitly directing to use get_task for long tasks. It lacks explicit when-not-to-use but provides strong contextual guidance.

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