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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds nothing beyond them: no indication of what a 'rank' response contains, how rankings are scoped by region/dateRange, cost or rate-limit behavior, or the errcode 501 failure mode hinted at in the schema. For an open-world data query with 12 filters, this is a bare label.

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 sentence is short but contains no informational payload — brevity here reflects under-specification rather than economy. Nothing is front-loaded because there is nothing to load, and the nested 'sortField' object syntax is never addressed.

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 12 optional parameters, a nested sortField object, no output schema, and an implicit ranking semantics that the agent must guess, the definition is wholly inadequate. An agent cannot determine what entity is ranked, by what metric, or how sorting interacts with the other filters.

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% and every parameter (region, shop_id, currency, language, pageSize, dateRange, sortField, creator_id, page_number, product_id, category_id, followers_range) is documented in the schema. The description adds zero parameter meaning, but per the high-coverage baseline a 3 is the appropriate score.

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 is a restatement of the tool name and title: 'TikTok Intelligence KD: livestream/rank API.' It hints at the resource (livestream rankings on TikTok via KD) but supplies no verb or scope statement, so an agent learns nothing the name does not already convey. The only value is a weak implicit contrast with siblings like kd_livestream_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?

There is no when-to-use guidance at all — no statement of when to pick this over nexscope_data_kd_livestream_detail, nexscope_tiktok_livestream_analytics, or the other KD rank tools (creator_rank, video_rank, product_rank, shop_rank). Selection must be inferred entirely from the identifier.

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