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

Annotations only supply readOnlyHint=false and openWorldHint=true; the description adds no behavioral context at all — no note that it hits an external patent database, no indication of what happens when both patentId and patentNumber are supplied, no rate/size behavior beyond what the schema already states. It conveys nothing beyond the annotations.

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 shortness here is under-specification rather than conciseness: a single label-like sentence that carries no actionable content.

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 patent lookup with no output schema, the agent needs to know what bibliography fields come back and how this differs from the sibling bibliography tools; none of that is present, leaving the definition largely incomplete.

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 both patentId and patentNumber are already fully documented, including the precedence rule and 100-item limit; the description adds nothing but the baseline of 3 applies when the schema does all the work.

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 almost verbatim ('Patent Intelligence ZY: bibliography API') without saying what the tool actually returns or does with the inputs. A reader cannot tell from this text how it differs from close siblings such as nexscope_data_zy_simple_bibliography or nexscope_data_zy_query_search_patent.

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 mention of alternatives (e.g., simple_bibliography vs. full bibliography), and no prerequisites. The agent must infer everything from the name.

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