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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context: the upstream source is Kalodata, and detail mode returns price range, sales, revenue, commission rate, listing/delisting time, and owning shop — valuable since there is no output schema. It does not disclose pagination caps, defaults applied when no filters are given, or what leaderboard mode actually returns.

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 keyword-stuffed and literally repeats the same phrases twice ('TikTok product ranking, TikTok bestseller chart, TikTok top products, kalodata product rank, TikTok product detail' appears verbatim twice), inflating length without adding information. The genuinely informative first sentence is front-loaded, but the bulk of the text does not earn its place.

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 no output schema and heavy sibling overlap, the description should explain mode selection, default behavior, and why to pick this over the many adjacent TikTok/Kalodata product tools. It covers the returned fields for detail mode but leaves leaderboard output, mode routing, and sibling differentiation unaddressed.

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 18 parameters, so the schema does the heavy lifting and baseline 3 applies. The description names a few output fields but adds no syntax, defaults, or interaction rules beyond the schema — notably it never explains that supplying productId switches to detail mode or how the nested sortField object should be shaped.

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: query TikTok product leaderboards via Kalodata, plus detailed data for a specific product via productId. That is clear about what it does. But the catalog contains many near-identical siblings (nexscope_data_kd_product_rank, nexscope_data_kd_product_detail, nexscope_tiktok_top_selling_products, nexscope_tiktok_product_analytics_api, nexscope_chuhaijiang_tiktok_product_detail) and the description never says how this differs, so an agent cannot disambiguate from the text.

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?

A long trigger-phrase list plus 'trigger this skill whenever their need involves viewing TikTok product leaderboards or detailed data for a specific TikTok product' gives implied usage. However, there are no exclusions, no mention of the alternative TikTok product tools, and critically no rule for how the agent selects between the two modes this tool bundles (leaderboard vs. productId detail lookup) — the schema's productId is the only hint.

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