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

Annotations provide almost nothing (readOnlyHint=false, openWorldHint=true) and no output schema exists, so the description carries the full burden — yet it discloses no return shape beyond a field list, no batch/limit behavior, and no handling of the patentId-vs-patentNumber precedence. It also implies a plain retrieval ('Returns...') while readOnlyHint=false suggests otherwise, which is an unexplained tension rather than a hard contradiction.

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?

A single efficient sentence with no waste, but its brevity is the result of under-specification rather than tight writing. Nothing is front-loaded about when to call the tool or what it costs.

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 tool with no output schema, two batch-capable parameters, and numerous overlapping siblings, the description should explain the return structure and the core-vs-detailed distinction. It leaves both unaddressed, so an agent cannot predict the response payload or pick between bibliography variants.

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%, with both patentId and patentNumber fully documented including comma-separated batching, the 100-ID/60,000-character caps, and the precedence rule. The description adds no parameter meaning at all, 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 sentence enumerates the returned fields (titles, abstracts, identifiers, dates, applicants, inventors, assignees, classifications), which conveys a bibliographic retrieval operation, but it never names the resource (patents) or the verb of retrieval explicitly. It also fails to distinguish this 'core' bibliography from close siblings such as nexscope_patent_detailed_bibliography, nexscope_data_zy_bibliography, or nexscope_data_zy_simple_bibliography. Purpose is inferable from the name only, not from the description.

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, no prerequisites, and no mention of any alternative tool. Given the dense cluster of bibliography and patent-search siblings, an agent is left to guess whether this is the right entry point. Usage is only implied by the tool name.

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