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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. However, the description adds nothing beyond that – no note on data freshness, coverage, pagination, or rate limits for a 25-parameter research query. It contributes zero behavioral context.

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 single sentence is terse and front-loaded, so there is no wasted text. But this is brevity by omission rather than economy – the length is inappropriate for a tool with 25 parameters.

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 tool with no output schema and no annotations covering semantics demands a substantive description. The one-line restatement leaves an agent with no understanding of what results look like, how the many range filters combine, or why one would call this instead of a sibling.

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%, so all 25 parameters are documented in the schema itself, justifying the baseline 3. The description adds no clarification of parameter interplay (e.g., priceBegin/priceEnd pairings, rating ranges) that would supplement the schema.

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 restates the name and title ('Temu Product Research: temu/product Query API') without adding a specific verb or scope. An agent learns only that it touches Temu products, and it cannot distinguish this from sibling tools like nexscope_temu_category_search or nexscope_data_gb_temu_goods_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 tool, when not to, or which sibling to prefer. With several Temu product/store/category search tools in the sibling list, the absence of routing guidance is a serious gap.

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