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

The description frames the tool exclusively as read behavior ('Query TikTok e-commerce product leaderboards', 'viewing', 'retrieve'), yet annotations declare readOnlyHint=false, signaling possible mutation — an agent cannot tell whether this is a safe read. The openWorldHint=true is corroborated by the named external provider, but no pagination limits (pageSize 5-100, pageNumber 1-5), rate-limit, or mode-dependent return behavior is disclosed.

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 keyword list is duplicated nearly verbatim in a single sentence ('TikTok product ranking, TikTok bestseller chart, TikTok top products, kalodata product rank, TikTok product detail' appears twice), which is pure noise. The useful scoping statements are buried after that repetition 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 an 18-parameter, dual-mode tool with a nested object and no output schema, the description omits the one thing an agent most needs: the rule for choosing between leaderboard queries and productId detail queries, and which filters apply to each. Enumerating the detail response fields partially compensates, but the mode/parameter relationship is left to inference.

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 schema already documents all 18 parameters, so the baseline is 3. The description adds some value by mapping outputs/inputs to concepts (region, currency, language, date range, price range, commission rate, listing time, owning shop), but it says nothing about the nested sortField object or which parameters belong to the leaderboard mode versus the detail mode.

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?

Specific verbs and resources: it distinguishes the two modes (leaderboard listing vs. detail-by-productId) and names the underlying source (Kalodata), plus the returned detail fields. It never differentiates itself from close siblings such as nexscope_tiktok_product_analytics_api, nexscope_data_kd_product_rank, nexscope_data_kd_product_detail, or nexscope_tiktok_top_selling_products, so an agent facing these overlapping tools gets no disambiguation.

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?

Provides concrete trigger context (TikTok product ranking/bestseller/top products, product detail/price/sales) and explicitly says to fire even when 'kalodata' isn't mentioned. Mode selection is only implied by the productId sentence — there is no statement of when NOT to use it or which sibling to prefer for rank-only or detail-only needs.

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