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 by structured data. The description adds that lookups are keyed by patent ID or publication number, but says nothing about what the response contains, whether the two parameters can be mixed, or what happens when neither is supplied.

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 first sentence is tight and front-loaded, but it is followed by a long comma-separated trigger-keyword list ('patent abstract retrieval, patent citation analysis, patent priority claims...') that restates the same idea a dozen times without adding routing value. The closing 'even if the user does not explicitly mention' sentence repeats the trigger condition already implied.

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 two-parameter read-only lookup with no output schema, the description is close to sufficient, and the keyword list incidentally hints at returned field families (applicant, inventor, classification, abstract, citations, priority, examiner). It still omits the one thing an agent cannot infer elsewhere: that a result exists per patent ID and that no results are returned when an unknown ID is passed.

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 100-value/60,000-character limits and that patentId takes priority over patentNumber. The description's 'by patent ID or publication number' is consistent and implies at least one identifier is required (required is empty), but it adds no format or conflict-resolution detail beyond the schema.

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 opening sentence gives a specific verb and resource — 'Query patent bibliographic (catalog) information ... by patent ID or publication number' — which an agent can act on directly. It does not, however, differentiate from closely named siblings such as nexscope_patent_core_bibliography, nexscope_data_zy_bibliography, or nexscope_data_zy_simple_bibliography; the word 'detailed' implies the distinction but never states it.

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 final sentence does state a usable trigger condition ('whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number'), which is a real usage context. But there are no exclusions and no routing to alternatives, in a sibling set containing at least four other bibliography tools — the agent is left to guess whether this or nexscope_patent_core_bibliography is correct.

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