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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the useful framing that this is a pre-sale market check in a target region, but says nothing about latency, quota/credit cost, whether an empty result means 'no risk', or what the detection response contains.

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?

The first sentence is a clean front-loaded purpose statement, but the body is a padded trigger-keyword dump with visible duplication ('patent infringement risk' and 'patent search' each appear twice, plus near-synonyms). A single trigger lexicon would carry the same routing signal in half the space.

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?

All four required parameters are schema-documented and the annotations cover the read-only profile, so the basics are in place. However, with no output schema, the description never says what the detector returns — a ranked list of patents, a similarity/risk score, or both — which is exactly the gap an agent needs filled before deciding to call it.

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% — region (US-only), topNumber (10-200), productTitle and productDescription (1000 char limits) are all documented in the schema. The description only re-expresses 'based on product information' and 'target market', adding no format, syntax, or quality guidance (e.g. how detailed the product description should be to get good recall). 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?

States a specific verb pair (detect/search) and a specific resource (utility/invention patents) grounded in product information. The 'utility/invention' qualifier lets an agent separate this from the design-patent siblings (nexscope_design_similarity_search, nexscope_ruiguan_detection_patent_design) and the trademark/copyright detectors without opening any schema.

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?

Provides a rich trigger list (infringement risk, similarity search, TRO risk analysis, pre-sale market screening) and explicitly extends the trigger to cases where the user never says 'utility patent'. It stops short of naming alternatives to route to instead — e.g. design-patent detection, trademark detection, or the raw patent-search siblings — so there is no when-not guidance.

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