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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds no behavioral context such as result caps, pagination/size limits (pageSize up to 1000, pids max 500), latency, quota, or whether calls consume credits. For a broad open-world query tool with 49 filters, that is a meaningful gap.

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 trigger list is duplicated almost verbatim ('Shopee product search, Shopee product selection, Shopee bestsellers, Shopee market analysis' appears twice), and the same concept is restated in three sentences. The useful content (marketplace coverage) is buried behind repetitive keyword stuffing.

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 49 parameters, one required field, no output schema, and thin annotations, the description should clarify the station mapping and return shape. Instead it references a 'site mapping table below' that is not present in the description, leaving a dangling instruction and no guidance on result volume or ordering behavior.

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 (price, sold, rating, category levels, dates, sort fields) is documented in the schema, so the baseline 3 applies. The description contributes nothing about parameter interaction, e.g. that 'station' is mandatory or how cidList's 'full path' grouping works.

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+resource ('Shopee product query and filtering') and enumerates the supported marketplaces, which clearly separates it from detail/download siblings such as nexscope_shopee_product_detail. It stops short of naming the closest alternatives explicitly, and the long brand framing ('YouYing') dilutes the core statement.

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-phrase list implies when to use it (product selection, bestsellers, market/category/keyword analysis, sales and price filtering), and it broadens to cases where the user never says 'Shopee'. However, it never states when NOT to use it or which sibling (e.g. nexscope_shopee_product_detail or nexscope_data_yy_shopee_get_product_infos) to pick instead, so routing among the Shopee tools is left to inference.

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