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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on data source recency, coverage, rate limits, or result shape — so it contributes no behavioral context of its own.

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 description is short but vacuous — it is under-specified rather than concise, containing no information an agent could act on. Length is fine; content is the problem.

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 9-parameter, 0-required search tool with no output schema and many near-identical Temu siblings, so the description carries real disambiguation burden. It delivers none of that, leaving the agent to infer intent from the parameter names alone.

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 each parameter carries a useful note (page/size cap of 10000, regionId sourced from sites[].regionId, 'do not silently translate' keyword guidance). The description adds no parameter meaning beyond the schema, 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 text restates the name and title ('Temu Intelligence GB: temu/keyword Search API') without saying what the search operates on or returns — keywords for a product, products for a keyword, or keyword metrics. It nominally names a verb and a resource, but an agent cannot distinguish it from siblings such as nexscope_data_gb_temu_goods_search or nexscope_geekbi_temu_keyword_search based on it.

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 statement of when to use this tool, what prerequisites exist (e.g. obtaining regionId from the site list), or which sibling to prefer. The only hint is embedded in the parameter schema, not the description, so guidance is effectively absent rather than misleading.

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