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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the source is the Nexscope patent database and that lookups are by ID or publication number, but it omits return format (URLs? binary? links?), batch behavior, and any failure mode for invalid IDs. With annotations carrying the safety burden, this is adequate but thin.

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 purpose is front-loaded well, but the bulk of the description is a keyword-stuffed trigger list with near-duplicates ('patent abstract images', 'patent drawings', 'patent illustrations', 'abstract drawing retrieval', 'patent image lookup'). Several of these phrases carry no distinct meaning and dilute the actionable 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 only two well-documented parameters and annotations covering safety, the description covers the basics. But there is no output schema and the description never states what is returned (image URLs, embedded assets, metadata) or how multiple IDs are handled in the response, which is the main remaining gap for an agent invoking it correctly.

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%, and the schema already documents the comma-separated list format, the 100-ID cap, precedence of patentId, and the 'at least one required' rule. The description only restates 'by patent ID or publication number,' adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 first sentence names a specific verb and resource: 'Retrieves patent abstract images (drawings) from the Nexscope patent database by patent ID or publication number.' This is clear and actionable. It does not explicitly differentiate itself from close siblings such as nexscope_patent_fulltext_images or nexscope_data_zy_abstract_image, so it stops short of a 5.

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 supplies trigger conditions ('Trigger when the user mentions patent abstract drawings...' and 'when the user needs to view the drawings or figures in patent documents'), which implies when to call it. However, it gives no when-not guidance and never names an alternative tool for related needs like full-text images, patent search, or image search, leaving the agent to infer sibling selection.

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