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

Annotations only provide readOnlyHint=false and openWorldHint=true, so the description carries the full behavioral burden and supplies nothing — no mention of pagination limits, region scoping, rate limits, or result shape. The description adds zero context beyond 'Search API', leaving an agent unable to distinguish this from a lookup or a write-shaped call.

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 one short sentence, but brevity here reflects under-specification rather than discipline — no salient constraint or scoping detail is front-loaded because none is present.

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 10-parameter, unauthenticated-looking, open-world search with no output schema and minimal annotations, this description is completely inadequate; an agent has no way to know what it returns or how to choose it over the other Temu 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% and the property descriptions are unusually informative (page*size limit, status codes, regionId sourcing, matchMode values). With the schema doing all the work, the baseline 3 applies; the description itself contributes no parameter guidance.

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 Intelligence GB: temu/goods Search API.' It does imply a search over Temu GB goods, but gives no verb+resource specificity beyond the name and no differentiation from the many closely related siblings (e.g. nexscope_geekbi_temu_goods_search, nexscope_data_gb_temu_goods_detail, nexscope_temu_category_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 guidance, no prerequisites, and no mention of alternatives, despite several near-duplicate Temu search tools in the sibling list. The agent is left to infer everything 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.