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

With readOnlyHint=false and openWorldHint=true already declared, the description adds nothing about what the call returns, whether a keyword is needed, rate limits, or the open-world dependency on Temu data. The phrase 'preserve provider business fields and extensions' is opaque and does not convey any actionable behavior.

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 a single short sentence with no padding, but it is also devoid of front-loaded useful information — brevity here comes from under-specification rather than tight drafting.

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 21-parameter, open-world query tool with no output schema, the description should explain what the operation returns and how filters interact. It provides none of that, leaving an agent to infer intent from the name 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% across 21 parameters, so the schema carries all parameter meaning (regionId must come from sites[].regionId, page*size <= 10000, etc.). The description adds nothing, which is acceptable but not helpful; baseline 3 applies.

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 sentence 'Execute the selected keyword research operation' largely restates the tool name and title without naming the resource domain (Temu keywords) or the concrete action (search/retrieve keyword metrics). It never distinguishes this from sibling Temu tools like nexscope_geekbi_temu_goods_search or nexscope_geekbi_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?

No when-to-use, when-not-to-use, or prerequisite information is given. An agent cannot tell from the description whether this tool requires a keyword, a category, or a region before calling, nor when a sibling Temu tool is the better choice.

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