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

The description claims a 'fixed read-only provider path,' while annotations declare readOnlyHint=false, so the description and annotations directly contradict each other. No useful behavioral context (result normalization, provider latency, rate limits, open-world coverage) is added beyond that misleading claim.

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 description is short, but its brevity reflects under-specification, not conciseness. The single sentence is boilerplate that conveys no actionable information about the 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 17-parameter search tool with no output schema, no annotation help beyond readOnlyHint=false, and zero parameter descriptions, the description provides none of what an agent needs: query semantics, pagination, date-filter syntax, or 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?

There are 17 parameters with 0% schema description coverage, including patterned fields like after/before and enum fields like type/status, yet the description explains none of them. With the schema providing no descriptions, the description must compensate, and it does not do so at all.

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 says only that the tool 'Returns normalized public ecommerce research data,' which does not state patent search, Google, or any search verb tied to the actual resource. It actively misleads by framing the tool as ecommerce research, when it is a patent search tool and sits among many patent siblings (nexscope_patent_search, nexscope_data_patents_search).

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 stated usage context, no conditions for choosing this tool over the many patent or search siblings, and no prerequisites. The agent is left with nothing but the tool name to guess when to invoke it.

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