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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description adds nothing: not whether this consumes quota, hits an external patent database, returns image URLs or binary data, or how failures behave. One sentence that only restates the title carries none of the burden for an unannotated-as-read 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 the single sentence earns nothing — it duplicates the tool name and title rather than front-loading purpose or constraints. Brevity here reflects under-specification, not efficiency.

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, no annotation coverage of safety semantics, and a non-read-only, open-world operation, the description should explain what is returned (image URLs? base64? per-patent mapping?) and any limits. None of that is present, so an agent cannot call it confidently.

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 patentId and patentNumber are fully documented in the schema, including the 100-item / 60,000-character limits and the patentId-over-patentNumber precedence. The description adds no parameter meaning, but baseline 3 applies when the schema does the work.

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 repeats the title verbatim ('Patent Intelligence ZY: abstract Image API') and never says what the tool actually does with the inputs — presumably retrieves abstract images for patents. No verb-plus-resource statement distinguishes it from siblings like nexscope_data_zy_fulltext_image, nexscope_data_zy_patent_image_search, 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 on when to use this tool versus the many adjacent patent-image tools (fulltext_image, patent_image_search, patent_abstract_image_data). The agent is left to 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.