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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered externally. The description adds useful scope ('complete specification/description content', 'one or more patents'), but says nothing about result format, per-patent failure behavior, or how gaps are surfaced when the replaceByRelated fallback is off.

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 strong lead sentence is followed by a bloated trigger list that repeats itself verbatim ('patent specification', 'patent full text', 'technical description', 'embodiment details' each appear twice). Roughly half the text is redundant keyword padding that does not help an agent decide or invoke.

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 a fully documented schema and read-only annotations, the description only needs to convey scope and any retrieval caveats. It conveys the scope ('complete specification/description content of one or more patents') but leaves the meaningful open questions—no output schema exists, so nothing describes what the returned payload looks like or whether untranslated text is returned.

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 three parameters—including the patentId priority rule and the replaceByRelated fallback—are already fully documented structurally. The description only echoes 'by patent ID or publication number' and implies batch retrieval; it adds no semantics beyond the schema, so 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'), a specific resource ('patent description (specification) data'), the source database, and the two lookup keys. However, in a tool family packed with near-identical patent retrieval siblings (patent claims, abstract, fulltext images, description_data_translation), it never states how it differs from them.

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?

Usage is conveyed only through a keyword trigger list ('when users mention patent specification, patent full text...'), plus a note that explicit 'Nexscope' mention is unnecessary. There is no guidance on when to pick this over nexscope_patent_description_data_translation or nexscope_data_zy_description_data, and no exclusions or prerequisites.

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