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

Annotations already declare this is a non-read-only (readOnlyHint=false), open-world (openWorldHint=true), non-idempotent write operation, so the safety profile is partly covered. However, the description adds nothing at all – no mention of long-running generation, callback/idempotency semantics, or cost – despite the tool clearly performing a generative write.

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?

Four characters is not conciseness but under-specification; there is no front-loaded purpose statement and no structure to speak of. Nothing here earns its place because nothing meaningful is said.

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 10-parameter generative write tool with no output schema and an open-world, non-idempotent profile, the description is completely inadequate. An agent has no idea what the tool returns, how long it takes, or how to choose it over sibling image tools.

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% across all 10 parameters, so the baseline is 3 even though the description contributes no parameter meaning. The schema labels themselves are terse (e.g. "语言", "输出分辨率") but they are at least present.

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?

"电商产品图" (e-commerce product image) is a noun phrase that essentially restates the tool name image_ecommerce; it never states a verb or whether the tool generates, edits, or retrieves such images. An agent cannot distinguish it from image_poster or image_create on this basis.

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?

No when-to-use, when-not-to-use, or alternative routing is given. With 29 siblings including image_create, image_poster, image_cutout, and image_enhance, the absence of any disambiguation guidance is a serious gap.

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