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

The description reads as a purely read-only lookup, yet annotations declare readOnlyHint=false, leaving the agent unsure whether the call consumes credits or has side effects; that tension is never resolved in the text. Beyond that, it adds nothing about query cost, rate limits, or result-set caps that the schema already constrains.

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 front-loaded sentence with no filler and the return contract stated up front. Its brevity is efficient rather than rambling, though the one sentence is thin for a nine-parameter 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?

For a nine-parameter search tool with a 12,000-character query DSL, sorting, and four collapse/dedup options, the description provides no orientation beyond 'it searches'. With no output schema, one sentence about publications and hit count is insufficient context for an agent to call it confidently.

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 detailed per-parameter text for queryText, sort, limit, offset, stemming and the collapse* family, so the schema carries the semantics. The description adds no parameter meaning of its own—it does not even hint that queryText accepts TACD:/TAC:/AND-OR-NOT syntax.

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?

A specific verb (Searches) and resource (Nexscope patents) with the return shape named (matching publications plus full hit count). It implicitly scopes the corpus to Nexscope's patent index, which separates it from nexscope_google_patent_search, but it never explicitly names the near-identical sibling nexscope_data_patents_search 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?

No guidance on when to choose this over the several other patent search tools in the catalog, and no prerequisites or preconditions stated. The only usage-relevant information (query DSL operators, pagination ceiling) lives in the schema, not the description.

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