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

The description calls this a 'Query API', implying a read-only lookup, while the annotations declare readOnlyHint=false. That is a direct semantic mismatch about whether the call mutates state, which is exactly the signal an agent relies on for safety. The description also provides no behavioral context of its own (no pagination, result shape, scope, or rate-limit notes).

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 short line with zero waste, but the brevity is under-specification rather than conciseness: there is no front-loaded intent, no scope, and nothing an agent can act on beyond the tool name. Efficiency without content.

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 25-parameter, open-world product search with no output schema and no behavioral disclosure needs the description to explain the query model (filter combinations, pagination behavior, what the results represent). None of that is present; only the rich input schema compensates. The definition is far short of complete for a tool of this complexity.

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% (25 params, each with an inline description covering pagination, sorting, ranges, and category IDs), so the schema fully carries parameter meaning. The description itself adds no parameter guidance, which is acceptable given the coverage — baseline 3.

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 essentially the title restated: 'Temu Product Research: temu/product Query API.' It contains a resource (Temu products) and a generic verb (query), but adds nothing beyond the name and does not distinguish this tool from close siblings such as nexscope_data_gb_temu_goods_search, nexscope_temu_product_source_query, or nexscope_data_eh_temu_store_query. This is tautology, not a specific statement of purpose.

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 exclusions, and no named alternative anywhere in the text. With dozens of Temu/1688/Amazon product-query siblings in the catalog, the agent gets no help deciding when this tool is the right one. No guidance at all.

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