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

Annotations declare readOnlyHint=false and openWorldHint=true, which is surprising for a filtering/query tool and is left unaddressed by the description — a reader gets no confirmation of whether this reads or mutates data. The description adds the dimension list but says nothing about result volume, pagination defaults, or whether calls consume quota, so it neither contradicts the annotations nor compensates for them.

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?

The purpose sentence is well front-loaded, but roughly half the text is a stuffed trigger-keyword list ('Temu store, Temu store analysis, Temu seller, Temu store ranking...') that repeats the same concept five ways without adding routing information.

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 29 optional parameters and no output schema, the description should say what a result row contains and how pagination/sorting defaults behave; it does neither, leaving the agent to infer the return shape. Coverage of the input dimensions is adequate, so it is incomplete rather than inadequate.

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 29 parameters, including sort-field syntax, site ID codes, and min/max range pairs, so the schema carries the semantics. The description's prose dimension list mirrors the schema rather than adding anything new, so 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?

States a specific verb and resource ('Filter Temu stores') and enumerates the filterable dimensions, so its function is immediately legible. It does not, however, distinguish itself from the other Temu store-retrieval siblings present in the catalog (e.g. nexscope_data_eh_temu_store_query), so an agent still has to guess which store query wins.

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 trigger list ('Temu store, Temu store analysis, Temu seller, Temu store ranking, Temu semi-managed store...') plus the closing sentence gives explicit invocation context, including the no-explicit-tool-name case. It offers no when-not guidance and never names an alternative tool, so it is clear context without exclusions.

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