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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description neither contradicts nor enriches them. It says nothing about response format, image resolution/URL behavior, whether missing images error or return empty, or batching limits — all non-obvious for an image retrieval 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?

It is short, but it is under-specified rather than concise: a single sentence that repeats the title and front-loads no actionable information. There is no wasted word because there is almost no content.

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, the description must explain what an 'abstract image API' returns (image URLs? base64? per-patent failure states?), and it does none of that. For a two-parameter retrieval tool sitting among dozens of patent and image siblings, this is inadequate.

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 both parameters (patentId, patentNumber) including their 100-item comma-separated limits and priority rule are fully documented in the schema. The description contributes nothing, but per the high-coverage baseline a 3 is appropriate.

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 is a verbatim restatement of the title ('Patent Intelligence ZY: abstract Image API') with no verb or explanation of what the tool actually returns. An agent can guess it fetches patent abstract images only by parsing the tool name itself; the prose adds nothing, and it does not distinguish this from near siblings such as nexscope_data_zy_fulltext_image or nexscope_patent_abstract_image_data.

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 whatsoever on when to use this tool, when not to, or which alternative (fulltext image, patent image search, abstract data translated) to prefer. The agent must infer selection purely from the tool name.

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