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

Annotations only declare readOnlyHint=false and openWorldHint=true, which flag a non-idempotent, externally-scoped call but say nothing about permissions, rate limits, or result shape. The description adds zero behavioral context beyond the title, so it does not relieve any of the ambiguity the annotations leave open.

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 brief, but brevity here is under-specification rather than conciseness — a single title fragment with no front-loaded statement of what the call returns or requires. Nothing is wasted, but nothing is earned either.

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 9-parameter tool with no output schema and thin annotations, the description should at minimum indicate what entity the search returns and how region/goods parameters scope it. That information is entirely missing, leaving the agent unable to decide between this and the many other Temu keyword/goods search tools.

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% across all 9 parameters, so the schema already documents page/size limits, sort/order, catIds, keyword, regionId, and the shelf-time bounds. The description contributes nothing to parameter meaning, but the baseline of 3 applies when the schema carries the load.

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 only restates the title ('Temu Intelligence GB: temu/keyword Search API') without a concrete verb or resource statement an agent could act on. The token 'keyword Search' hints at a keyword-based lookup over Temu data, but scope, returned entity, and result type are never stated, and it is indistinguishable from siblings like nexscope_data_gb_temu_goods_search or nexscope_geekbi_temu_keyword_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 when-to-use, when-not-to-use, or alternative-tool guidance at all. With dozens of near-identical Temu and keyword-search siblings in the namespace, the absence of any routing signal leaves the agent to guess from the name alone.

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