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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The phrase "preserve provider business fields and extensions" hints that the response passes through raw provider fields rather than a normalized shape, which is modest added value, but nothing is said about pagination limits, rate limits, or result shape.

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?

A single short sentence with no padding, but it is under-specified rather than economical, and the one substantive claim (provider field preservation) is buried in vague phrasing rather than front-loaded.

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, fully-optional filter tool with openWorld access and no output schema, the description should convey what a call returns (keyword rows with search volume, competition, etc.) and how paging behaves. None of that is present, leaving the agent to infer the result shape entirely.

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 21 parameters, including notes like regionId coming from sites[].regionId and page*size <= 10000, so the schema carries the semantics. The description adds nothing beyond the schema; 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 restates the title in generic terms ("keyword research operation") without ever saying it searches Temu keywords, what entity it returns, or what makes it different from the many sibling keyword/temu tools (e.g. nexscope_data_gb_temu_keyword_search, nexscope_geekbi_temu_goods_search). An agent reading only the description cannot tell the verb+resource apart from a dozen neighbors.

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, no when-not-to-use, and no named alternative. With seven geekbi_temu siblings plus several temu keyword tools in the list, this is exactly the case where routing guidance is required, and none is given.

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