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. The description adds nothing beyond that — no indication of pagination limits, data freshness, what a 'store' record contains, or quota/rate behavior for an open-world query.

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 shortness here is emptiness rather than conciseness — a single redundant fragment that duplicates the title. There is no front-loaded purpose statement because no purpose is stated.

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 29-parameter, optional-heavy query tool with no output schema demands far more explanation than a title echo. An agent cannot tell what it retrieves, what a result row looks like, or how the many filters compose.

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?

All 29 parameters are documented in the schema at 100% coverage, so the schema carries parameter meaning and the baseline of 3 applies. The description contributes no additional semantics (e.g., how range min/max pairs or site ID lists interact).

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 merely restates the title ('Temu Product Research: temu/store Query API') without a real verb-plus-resource statement of what the tool returns. It never distinguishes this from close siblings such as nexscope_temu_store_source_query, nexscope_data_eh_temu_product_query, or nexscope_geekbi_temu_mall_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 guidance on when to use this store-level query versus the many other Temu siblings (product query, category search, mall search, site list). No prerequisites, exclusions, or alternative routing are given.

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