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

The description adds no behavioral context beyond the call signature: no indication of what the 'detailed' record contains, no cost/quota/rate-limit notes, and no error behavior. Annotations only declare openWorldHint=true and readOnlyHint=false; the description's 'query' framing neither confirms nor clarifies why a read appears non-read-only, leaving that discrepancy unaddressed.

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 core intent is one sentence, but it is buried under a ~25-item trigger keyword list ('patent applicant queries, patent inventor queries, patent classification codes, patent abstract retrieval, patent citation analysis...') that is largely redundant with the tool name and siblings. The padding makes the definition harder to scan, not easier.

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 two-parameter lookup with fully documented schema, the definition is callable as written. What is missing is what an agent needs before choosing it: which bibliographic fields are returned and why to pick this over the core/simple bibliography variants when no output schema is provided.

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 both parameters including the patentId-over-patentNumber precedence and the 100-value/60,000-character limits. The description only restates 'by patent ID or publication number' and adds no format or interpretation guidance 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 first sentence gives a specific verb and resource: query patent bibliographic/catalog information by patent ID or publication number, from the Nexscope patent database. However, it never distinguishes itself from the many sibling bibliography tools (nexscope_patent_core_bibliography, nexscope_data_zy_bibliography, nexscope_data_zy_simple_bibliography), so an agent cannot tell what 'detailed' adds over 'core' or 'simple'.

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?

It states a trigger condition ('whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number') and reiterates that explicit mentions are not required. But there is no when-not guidance and no routing to alternative tools, even though three near-identical bibliography siblings exist. The long keyword enumeration adds noise rather than decision criteria.

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