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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on pagination limits (pageNumber 1-5), rate limits, or what the ranking is based on. 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?

It is short, but that brevity comes from under-specification rather than efficiency — the single sentence merely echoes the name and title, so no sentence actually earns its place by conveying information.

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 17-parameter, zero-required, nested-object tool with no output schema demands far more description than a title echo. The agent has no idea what the ranking returns, how pages relate, or what sortField accepts — the description is completely 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?

With 17 parameters and 100% schema description coverage, the schema itself documents every field, so the baseline of 3 applies. The description adds no semantic framing for the rich filter set (dateRange, sortField, revenue_range, is_affiliate), leaving the agent entirely dependent on the schema.

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 almost verbatim: "TikTok Intelligence KD: product/rank API." It implies a product ranking resource for TikTok, but there is no verb describing what the tool actually does (list? rank by what metric?) and no differentiation from siblings such as nexscope_data_kd_shop_rank, nexscope_data_kd_video_rank, or nexscope_tiktok_top_selling_products.

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 prerequisites, and no mention of alternatives. The agent cannot tell from the description why it would pick this ranking endpoint over the many other KD ranking siblings (shop_rank, creator_rank, video_rank, livestream_rank).

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