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. However the description adds nothing on top: it does not say whether it screens a product against existing utility patents, what a match result looks like, or how the external patent corpus is queried. For an open-world screening call, that is a real gap.

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 sentence with zero waste, but it is under-specified rather than concise — the brevity comes from having nothing to say. There is no front-loaded statement of what the call returns or when it fires.

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 four-required-parameter, open-world patent risk query with no output schema needs the description to explain what the returned matches mean and how to interpret them. The description provides none of this, leaving the agent unable to judge whether the tool answers its question at all.

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 region, topNumber, productTitle and productDescription all documented in-schema including defaults and length limits. The description adds no meaning beyond that, 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 is a restatement of the title: 'IP Risk Detection RG: utility Patent Detection API.' It does gesture at a domain (utility patent detection) but supplies no verb, no scope, and no indication of what the call actually does with a product title and description. Nothing distinguishes it from close siblings like nexscope_utility_patent_detector or nexscope_data_rg_detection_patent_design.

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 preconditions, and no mention of alternatives in a catalogue containing several adjacent IP-risk tools (patent design detection, trademark detection, copyright detection, patent search). An agent has no basis to prefer this tool over those.

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