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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description contributes nothing beyond that — no note on data freshness, coverage of patent offices, licensing/credential requirements for an external patent provider, or result limits for the 100-ID batch.

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?

One short sentence with no waste, but its brevity comes from saying almost nothing rather than from efficient editing. It is front-loaded only in the trivial sense that there is nothing else to load.

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 description is the only place an agent could learn what 'bibliography' returns (title, assignee, dates, IPC codes?), and it says nothing. For a batch lookup tool taking up to 100 IDs against an external patent database, the agent is left guessing both output shape and how this differs from adjacent bibliography endpoints.

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%: both patentId and patentNumber are documented in the schema, including comma separation, the 100-item cap, and the precedence rule when both are supplied. The description adds nothing beyond that, so the baseline 3 applies — 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 is the title verbatim: 'Patent Intelligence ZY: simple Bibliography API.' It names a resource but no verb and no scope, so it effectively restates the name/title rather than explaining what the call returns or does. It does not distinguish itself from the many sibling bibliography tools (nexscope_data_zy_bibliography, nexscope_patent_core_bibliography, nexscope_patent_detailed_bibliography), which is exactly the ambiguity an agent must resolve.

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 prerequisites or alternatives. The word 'simple' hints it is a lighter variant, but the description never says to prefer the detailed bibliography tool when more fields are needed, nor when this one is sufficient.

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