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

The description discloses nothing beyond the name: no data source, freshness, pagination behavior, auth requirements, or what a ranking entry contains. Annotations only supply readOnlyHint=false and openWorldHint=true, leaving the actual behavioral profile of this query-style ranking endpoint unexplained.

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?

It is a single short line with no padding, but it is pure restatement of the title rather than a front-loaded statement of what the tool does. Brevity here reflects under-specification, not efficient communication.

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 11-parameter, nested-object, open-world ranking endpoint with no output schema, the description provides none of the orientation an agent needs — not the entity ranked, the metric ranked by, nor the response shape. It is wholly inadequate for this complexity.

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?

All 11 parameters carry schema descriptions at 100% coverage, so the schema already explains region, currency, dateRange, shop_type, pageSize, pageNumber bounds, and category filters. The description adds no parameter meaning of its own, so the high-coverage baseline of 3 applies.

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 restates the title verbatim ("TikTok Intelligence KD: shop/rank API") with no verb describing the action and no explanation of what data comes back. "shop/rank" faintly suggests a ranking of TikTok shops, but that is inference from the name, not a stated purpose, and it does nothing to separate this from siblings such as nexscope_data_kd_shop_detail or nexscope_tiktok_shop_analytics.

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 conditions, and no mention of any alternative tool. Given the crowded sibling set (shop_detail, shop_analytics, plus several tiktok/chuhai jiang shop ranking tools), an agent has no way to know when this ranking endpoint is the right choice.

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