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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds nothing beyond that — no indication of data freshness, coverage by region, ranking window semantics, or pagination limits, despite this being an external open-world data query.

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 earns no place — it duplicates the title and conveys no operational information. Brevity here reflects under-specification rather than efficient front-loading.

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 14 optional parameters, a nested object, no required fields, and no output schema, this tool needs real guidance on what the ranking represents and how to scope a query. The description supplies none of that, leaving the agent to guess from parameter names alone.

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 14 parameters, including the nested sortField object and the range filters, so the schema carries parameter meaning on its own. The description contributes zero additional semantics, which lands at the baseline for fully documented schemas.

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 essentially the title restated: 'TikTok Intelligence KD: video/rank API.' It names a resource area (video ranking) but never states the verb, the metric being ranked, or what the response contains. Against siblings like nexscope_data_kd_video_detail, nexscope_tiktok_video_rank, and nexscope_data_et_list_video_rank, an agent gets no basis for choosing this one.

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, when-not-to-use, or alternative routing information anywhere in the description. The agent is left to infer usage entirely from the tool name among hundreds of TikTok and e-commerce siblings.

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