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

Annotations declare readOnlyHint=false and openWorldHint=true, which for a ranking/data query is surprising and needs explaining — the description offers nothing. No mention of rate limits, pagination constraints (pageNumber capped at 5, pageSize 5-100), data freshness, or what the sortField gateway actually accepts. The description adds zero behavioral information 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 single sentence is not verbose, but for a 13-parameter, open-world tool it is severely under-specified rather than concise. Length is not wasteful — it simply fails to carry the load the tool requires.

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?

A 13-parameter ranking API with a nested object parameter, no output schema, no enums, and no required fields demands explanation of what is returned and how ranking/filtering combine. The definition provides none of that, so an agent cannot confidently construct a call or interpret the result.

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%, so the schema already documents all 13 parameters, and per the baseline rule a 3 applies when the schema does the heavy lifting. The description contributes nothing on top, leaving genuinely ambiguous parameters such as the nested sortField object ("subject to those actually accepted by the gateway") and unenumerated range fields like revenue_range and followers_range unexplained.

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 and name verbatim: "TikTok Intelligence KD: creator/rank API." It signals the domain (TikTok) and a nominal resource (creator rank), but supplies no verb describing what the tool actually does or returns — a ranking list of creators? a single creator's rank? With dozens of near-identical TikTok creator/ranking siblings, the name alone does not disambiguate.

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 exclusions, and no named alternative. The sibling set contains at least fifteen TikTok creator/ranking tools (nexscope_data_kd_creator_detail, nexscope_data_cj_creators_rankings_growth, nexscope_chuhaijiang_tiktok_creator_rankings_commercial, nexscope_tiktok_creator_analytics, etc.), so an agent has no basis for choosing this one over any of them.

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