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 mention of query syntax constraints, result caps derived from limit/offset, or deduplication behavior that materially affects results.

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 short by omission rather than by discipline — a single tautological sentence that duplicates the title and front-loads nothing useful about a 9-parameter search tool.

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?

A 9-parameter tool with deduplication, sorting, stemming, and a complex Boolean queryText grammar has no output schema and a description that says nothing. The schema carries nearly all the burden; the description leaves the agent without context on result shape or selection rationale.

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 every parameter documented inline including enum-like allowed values and the limit+offset <= 20,000 constraint. 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 verbatim ('query Search Patent API') without stating what the tool actually retrieves or how it differs from other patent search tools. An agent learns only that it is a patent search API call, nothing about scope or result type.

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?

No when-to-use guidance, no exclusions, and no reference to any of the many sibling patent tools (nexscope_data_patents_search, nexscope_patent_search, nexscope_google_patent_search, nexscope_zhihuiya_*). The agent has no basis to choose this over an alternative.

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