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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds only 'preserve provider business fields and extensions' — an opaque clause that does not clarify what comes back, whether pagination is capped, or how provider-native fields should be interpreted.

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?

One short sentence, so there is no bloat, but also no front-loaded substance — the single sentence is generic filler rather than scope or guidance. Brevity here reflects under-specification rather than economy.

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 54-parameter search endpoint with no output schema, the description leaves the agent guessing about result shape, page/size interaction, and sibling selection. It should at minimum state that this is the Temu product listing query and how it relates to the keyword/category/image search siblings.

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 54 parameters, including min/max pairing rules, enums for status/matchMode/hostingMode, and the regionId-vs-siteId warning. The description contributes nothing beyond that, which is the baseline 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 phrase 'Execute the selected product search operation' largely restates the tool name rather than defining scope: it never says Temu, never says what a 'selected operation' is, and never distinguishes this from siblings such as nexscope_geekbi_temu_keyword_search, nexscope_geekbi_temu_category_search, or nexscope_geekbi_temu_goods_image_search. Only 'product search' anchors the resource.

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 routing at all. With seven other geekbi_temu siblings in the list, an agent has no basis for choosing this tool over the keyword, category, mall, or image-search variants.

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