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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that—no note on whether the lookup is by ID or publication number at call time, no batching/pagination behavior, no failure mode for unknown IDs—which is a meaningful gap given 100-item batch limits.

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 short, but brevity here is under-specification rather than conciseness: the single sentence contains no actionable information beyond the tool's title. There is nothing to front-load because nothing substantive is said.

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 and four near-identical bibliography siblings, the description needed to explain what this variant returns (e.g., vs. simple/core/detailed bibliography) and when to pick it. It does neither, so an agent cannot confidently route to this tool rather than a sibling.

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 itself documents the comma-separated batch format, the 100-item cap, the 60,000-char limit, and the patentId-over-patentNumber precedence. The description contributes no additional parameter meaning, 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 description restates the title ('Patent Intelligence ZY: bibliography API') with no verb describing what is retrieved or in what form. It does signal the resource domain (patent bibliography) and the vendor (ZY), but nothing distinguishes it from close siblings such as nexscope_data_zy_simple_bibliography, nexscope_patent_core_bibliography, or nexscope_patent_detailed_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 guidance on when to call this vs. the many other bibliography tools, no prerequisites, no note that both params are optional (so a fully unscoped call may be invalid or expensive), and no mention of the patentId-over-patentNumber priority rule. The agent is left to infer everything.

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