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

Annotations declare a non-read-only, open-world operation, and the description adds the meaningful clause that comparison runs against a global database across 25+ jurisdictions. It stops there: no mention of whether calls consume credits, whether enableRadar analysis changes latency or output, or how the detection verdict is delivered, all of which matter given readOnlyHint=false.

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 core capability is stated in the first sentence, and the routing keywords follow it rather than preceding it. The second sentence is somewhat keyword-list-heavy and could be tightened, but every clause serves a disambiguation purpose.

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 10-parameter detection tool with no output schema and only two annotations, the description should say what comes back — matched patents, similarity scores, risk levels — and whether enableRadar materially changes that. As written an agent can decide to call it but cannot anticipate the result shape.

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% — every one of the 10 parameters carries its own description with examples. The description adds nothing beyond the implicit link between 'product image' and imageUrl, and does not explain the interaction between queryMode, enableRadar, and topNumber. 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 first sentence names a specific verb (detect), resource (design patent infringement risk), method (product image compared against a design patent database), and scope (25+ jurisdictions). The phrasing separates it implicitly from adjacent siblings like nexscope_utility_patent_detector and nexscope_ruiguan_trademark_graphic_detection by specifying 'design patent' and visual comparison.

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?

The trigger list ('design patent detection, patent infringement check, patent risk analysis, TRO case lookup...') plus the explicit fallback ('even if the user does not explicitly say design patent') gives strong when-to-use guidance for an agent doing routing. However, it never states when NOT to use it — e.g., to route to the utility patent or trademark detectors for non-design-IP questions.

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