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

The description states a pure retrieval operation ('Retrieve ... data') with no side effects, yet the annotation declares readOnlyHint=false, an inconsistency between the stated behavior and the structured hint. Beyond that conflict, the description discloses nothing about rate limits, output size limits, pagination, or auth needs.

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 useful content is confined to the first sentence; the second is a keyword-stuffed trigger list that repeats terms ('patent specification' and 'patent full text' each appear twice) and adds routing boilerplate rather than information. Roughly half the text does not earn its place.

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 simple three-parameter lookup tool with fully documented parameters and no output schema, the input side is adequately covered, and the bulk aspect ('one or more patents') is conveyed. However, the read/write discrepancy with the annotation and the absence of any alternative-tool routing leave the definition only minimally complete.

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 coverage is 100%: patentId, patentNumber, and replaceByRelated all carry detailed inline descriptions covering the priority rule, comma-separated bulk values, and the substitution flag. The description only restates that lookup is 'by patent ID or publication number' and adds no semantics the schema does not already provide, 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 gives a specific verb (Retrieve), resource (patent description/specification data), source (Nexscope patent database) and lookup keys (patent ID or publication number). It does not, however, distinguish itself from close siblings such as nexscope_patent_description_data_translation, nexscope_patent_claims, or nexscope_patent_fulltext_images, whose scope overlaps with the 'patent full text' wording used here.

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 phrases and a general condition ('whenever they need to view the complete specification/description content of one or more patents'), which implies when to call it. It gives no when-not guidance and never routes the agent to the natural alternatives (translation variant for non-English, claims tool for claim text, search tool when the patent ID is unknown).

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