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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description's 'Filter' framing is consistent with a safe read. Beyond that it adds no behavioral context: no pagination behavior, no indication of what the result set contains or how large it can be, no rate-limit or coverage notes.

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 first sentence is dense and front-loaded with the useful content, but the following two sentences are keyword-stuffed trigger lists that repeat 'Temu products', 'Temu product selection', 'Temu product query', and 'temu items' without adding distinct 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?

For a 25-parameter read-only filter query with full schema coverage, the description covers the filtering surface adequately. It is still thin on what comes back (no output schema exists) and on how this tool relates to the many other Temu data endpoints in the catalog.

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?

With 100% schema description coverage, the baseline is 3. The description's dimension list (front/backend categories, total/weekly/daily sales, fully-managed/semi-managed, tags) loosely mirrors the schema but supplies no syntax, defaults, or range-combination rules beyond what the schema already states.

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?

A specific verb (Filter) plus resource (Temu products) and a full enumeration of the filterable dimensions, so the agent can tell what it does. It never distinguishes itself from close siblings like nexscope_temu_store_source_query or nexscope_temu_category_search, leaving boundary selection to guesswork.

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 'Triggered when users mention...' sentence gives keyword-level invocation cues, which is real usage guidance. But the cues are broad catch-alls ('viewing sales/ratings/prices', 'searching for products') that do not name alternatives or exclusions, so an agent has no rule for choosing this over the Temu store or category tools.

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