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

Annotations declare readOnlyHint=false and openWorldHint=true, which is already surprising for a "search" tool, yet the description neither explains what mutation is implied nor clarifies that it is a read query. "Preserve provider business fields and extensions" is opaque jargon that gives the agent no usable behavioral context (pagination bounds, result caps, rate limits).

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 with no padding, but it is under-specified rather than lean: the second clause about "provider business fields and extensions" consumes space without conveying meaning an agent can act on.

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?

With 18 optional filter parameters, no output schema and no required params, the description must convey what a result row contains and how to build a meaningful query; it does neither. An agent must read the entire schema and guess at the return shape.

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 18 parameters, including range-pair constraints and the regionId-vs-siteId warning, so the schema carries parameter meaning. The description adds nothing beyond that, which is the expected baseline 3.

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 tool's name in abstract terms: "Execute the selected category research operation" never says this searches/ranks Temu categories by keyword, price, sales or item counts. Nothing distinguishes it from the multiple near-identical siblings (nexscope_temu_category_search, nexscope_data_gb_temu_category_search, nexscope_data_eh_temu_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?

"The selected category research operation" faintly hints at a multi-step workflow but no condition for choosing this tool over its siblings is given. There is no mention of prerequisites such as resolving regionId via nexscope_geekbi_temu_site_list, nor of when to use category research rather than keyword or goods search.

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