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

Annotations only declare readOnlyHint=false and openWorldHint=true, which is ambiguous for what is clearly a search/detection operation; the description adds nothing to clarify that this is a read-style query that returns recalled patents plus an optional AI infringement radar analysis. It also omits any mention of cost, latency, external patent database dependency, or what the recall results contain. No annotation contradiction, but zero added transparency.

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 it is a single tautological fragment with no front-loaded statement of purpose, inputs, or return behavior. Brevity here comes from under-specification rather than economy of expression.

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?

This is a 10-parameter, image-driven patent search with no output schema and no annotation clarity on whether it mutates state, yet the description conveys none of that. The rich schema compensates for parameter documentation, but an agent still cannot tell from the description what the tool returns or when to pick it over its near-duplicate siblings.

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% and all ten parameters carry detailed descriptions (queryMode modes, topLoc LOC regex, patentStatus filter values, region list), so the schema does the heavy lifting. The description itself contributes no additional parameter meaning, which is the baseline 3 case.

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 tool name and title: 'IP Risk Detection RG: detection Patent Design API.' It never says in plain language that this performs a design-patent image search against patent databases, nor does it distinguish the tool from siblings such as nexscope_ruiguan_detection_patent_design, nexscope_data_rg_utility_patent_detection, or nexscope_design_similarity_search. Only the schema's imageUrl parameter hints at what the tool actually does.

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 guidance on when to use this tool, when not to, or which sibling to prefer for design-patent vs utility-patent vs trademark detection. An agent has to infer usage entirely from the name and the schema, which is not sufficient given the many overlapping IP-detection siblings.

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