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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing about result volume, pagination semantics (pageSize max 100 is only in the schema), or whether an empty filter returns the full store universe — modest incremental value only.

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 useful first sentence is followed by a long, repetitive trigger keyword list ('Temu store, Temu store analysis, Temu seller, Temu store ranking...temu stores, Temu store query') and a final sentence that restates the same trigger condition in prose. Roughly half the text is redundancy, pushing the actionable content out of a front-loaded position.

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 29-parameter, no-required-field query tool with no output schema, the description covers the filterable axes but says nothing about default behavior (what sorting/result set you get with zero filters) or result shape. Given the annotations carry the read-only safety profile, this is adequate but not complete.

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% and every filter (ranges, sortBy, siteId, isLocal) is documented in the schema itself, so the baseline is 3. The description's dimension list loosely mirrors those parameters but adds no format, unit, or range-combination semantics 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?

The first sentence states a specific verb and resource (filter Temu stores) and enumerates the filterable dimensions, so the agent knows exactly what the tool returns. It does not, however, distinguish itself from near-neighbours like nexscope_data_eh_temu_store_query or nexscope_geekbi_temu_mall_search, which the description never mentions.

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?

Explicit trigger conditions are given: 'trigger this skill whenever they are looking for stores on Temu, filtering store data, or analyzing store performance', plus a keyword list for fuzzy matching. There are no when-not conditions and no routing to alternative tools (e.g. the Temu product query sibling), so it stops short of full guidance.

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