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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond that — no indication of what a 'fulltext image' record contains, whether images are URLs or binaries, licensing/paywall constraints, or pagination behavior.

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 a single short sentence with no wasted words, but this is under-specification rather than conciseness — the entire sentence is a restatement of the title, so nothing is front-loaded because nothing 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 tool with four parameters, no output schema, and no explanation of the returned image data, the description leaves the agent without the information needed to invoke it confidently or interpret results. Annotation coverage of the safety profile does not compensate for the missing purpose and return-value context.

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 all four parameters (limit, offset, patentId, patentNumber) are documented in the schema and the baseline of 3 applies. The description contributes no additional meaning, such as whether patentId and patentNumber are interchangeable or which identifiers are accepted.

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 tool title, 'Patent Intelligence ZY: fulltext Image API.' It implies retrieval of patent full-text images but states no verb or object beyond the name itself, and it does nothing to distinguish this from close siblings such as nexscope_data_zy_abstract_image, nexscope_data_zy_patent_image_search, or nexscope_patent_fulltext_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?

There is no when-to-use statement, no exclusion, and no named alternative. With roughly a dozen patent-image siblings in the listing (abstract image, image search, fulltext images, zhihuiya image search), an agent has no basis for choosing this tool over another.

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