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

Annotations already state readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the content type and view/download intent, but does not disclose return format, pagination behavior, authentication needs, or whether images are returned as URLs or binary data. It does not contradict the annotations.

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 in the first sentence, but the rest is heavily repetitive keyword stuffing, listing patent images, drawings, diagrams, and charts multiple times. The trigger guidance is useful but could be much shorter without losing meaning.

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 no output schema, the description does not explain the return format, such as whether results are image URLs, thumbnails, or downloadable files. It also implies that a patent ID or publication number is needed but does not clarify this requirement despite all schema parameters being optional.

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 the schema already documents all four parameters. The description reinforces that retrieval can use patent ID or publication number, but it does not add meaning for limit or offset beyond what the schema provides.

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 (Retrieve), resource (fulltext images), source (patent documents), and identifiers (patent ID or publication number). This is clear enough to distinguish it from patent text tools, but it does not explicitly contrast with nearby siblings such as abstract-image or image-search tools.

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 gives explicit trigger conditions, including the instruction to use it even when the user does not mention 'fulltext drawings' but needs visual content from specific patents. It lacks when-not guidance or explicit alternatives such as patent image search versus fulltext image retrieval.

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