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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered and the bar is lower. The description adds nothing beyond that: no note on batch semantics (schema allows up to 100 IDs), no indication of whether abstracts are truncated or whether missing patents are silently omitted from the response.

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?

It is a single sentence with no filler, but the one sentence spent on a return-field enumeration leaves the description under-specified for a tool with three near-duplicate siblings. There is nothing to front-load because no purpose statement was written.

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 no output schema, the field list is a genuine contribution toward describing returns. However, it omits pagination/limits, batch behavior on partial misses, and differentiation from the detailed and simple bibliography siblings, which an agent needs in order to choose correctly.

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% and both parameters are documented in the schema, including the 'patentId takes precedence' rule, so the baseline of 3 applies. The description contributes no additional parameter meaning such as which identifier type to prefer in a given workflow.

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 sentence enumerates what comes back (titles, abstracts, identifiers, dates, applicants, inventors, assignees, classifications) rather than stating the action, e.g. 'retrieve core bibliographic metadata for patents'. It conveys the domain but gives no basis for telling it apart from close siblings like nexscope_patent_detailed_bibliography or nexscope_data_zy_simple_bibliography.

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?

There is no when-to-use guidance at all, and no mention of the sibling tools that overlap most (simple vs detailed bibliography, patent search, family/citation tools). An agent must infer the selection rule from the difference in field lists alone.

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