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

The annotations declare readOnlyHint=false and openWorldHint=true, so the safety/scope profile is already stated, but the description adds nothing on top: no indication of what data is ranked, how it is paginated, whether results are cached, or what errors like errcode 501 mean in this context. It does not contradict the annotations, but it contributes zero behavioral context.

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 that reflects under-specification rather than economy — it is a duplicate of the title and front-loads nothing useful. Nothing is wasted, but nothing is communicated either.

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 a 12-parameter, filter-heavy ranking API with no output schema and open-world annotations, the description provides no information about what the ranking measures, what the response contains, or how sort/filter parameters interact. It is grossly inadequate for the tool's 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?

Schema description coverage is 100% across 12 parameters, including the sortField structure hint and pageNumber range caveat, so the schema carries parameter meaning adequately. The description adds no syntax or format guidance beyond it, which is the baseline case for high coverage.

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: livestream/rank API.' It implies a ranking of TikTok livestreams but supplies no verb, no scope, and no differentiation from close siblings such as nexscope_data_kd_livestream_detail or nexscope_data_kd_creator_rank. An agent cannot tell what the tool actually returns.

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 when-not-to-use, and no mention of any alternative among the many ranking and livestream tools in the sibling list. The agent is left to infer everything from the tool name.

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