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

Annotations already declare this to be a read-only, non-destructive, open-world tool, so the safety profile is covered. The description adds useful context about what detail data can be retrieved (revenue, sales volume, channel revenue, creator collaboration count) but does not disclose rate limits, authentication needs, pagination behavior, or other operational traits beyond the annotations.

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 purpose is front-loaded in the first two sentences, but the description is padded with a long, highly repetitive trigger-keyword list that duplicates phrases like 'TikTok shop ranking,' 'TikTok shop leaderboard,' and 'TikTok top shops.' This keyword stuffing reduces clarity and fails the conciseness standard.

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?

The tool has 12 optional parameters, two distinct usage modes, and no output schema, so the description should do more to explain mode selection and return values. It partially covers what the detail mode returns and how shopId is used, but does not describe leaderboard output fields or clarify how to invoke each mode cleanly.

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 coverage is 100%, so the input schema already documents all 12 parameters thoroughly. The description adds some mode-level meaning by mentioning region, currency, language, dateRange, and shopId, but does not explain many other parameters such as sortField, pageSize, pageNumber, shop_type, category filters, or revenue_range.

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 clearly states two specific capabilities: searching TikTok Shop store leaderboards and querying detailed store information via shopId. It names the resource and the data source (Kalodata), though it does not explicitly differentiate this tool from sibling tools such as nexscope_data_kd_shop_rank or nexscope_data_kd_shop_detail.

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 description provides extensive trigger phrases indicating when the tool should be invoked, including when 'kalodata' is not mentioned. However, it does not state when to avoid this tool or how to choose between this umbrella tool and more specific sibling tools like nexscope_data_kd_shop_rank and nexscope_data_kd_shop_detail.

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