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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered by structured data. The description adds nothing beyond that — no note on pagination limits, the errcode 501 behavior, quota/rate limits, or what the ranking response contains. It does not contradict annotations, but its contribution is essentially zero.

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 single fragment is brief but not concise in the useful sense — it is under-specified rather than economical. No front-loaded statement of what the tool returns or when to call it.

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 11 parameters including a nested sortField object, page-number range constraints, and no output schema, the definition needs to explain return shape, sorting semantics, and paging behavior. The description supplies none of this, leaving the agent unable to invoke the tool meaningfully beyond guessing from parameter names.

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 all 11 parameters, so the schema already documents region, currency, dateRange, pageSize, shop_type, sortField, and the category filters. The description contributes no additional meaning, which is the baseline expectation when the schema does all the work.

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 description "TikTok Intelligence KD: shop/rank API" only restates the name and title, adding the words "shop/rank" which hint at a shop leaderboard but never state what is ranked, over what period, or by what metric. It does not distinguish this tool from sibling ranking tools such as nexscope_data_kd_product_rank, nexscope_data_kd_creator_rank, or nexscope_chuhaijiang_tiktok_shop_rankings_top_selling.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text why it would pick this ranking endpoint over the many other KD and CJ ranking siblings.

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