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

The description calls this a 'fixed read-only provider path,' yet the annotations declare readOnlyHint=false, directly contradicting the read-only claim. Beyond that contradiction, it discloses nothing about pagination, rate limits, result ordering, or what the fixed provider path implies.

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?

One short sentence is technically concise, but it is under-specified rather than efficient — it spends its only sentence on boilerplate instead of the information the agent needs.

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 8 undocumented parameters, four unexplained enums, no output schema, and contradictory annotations, the description leaves the caller unable to invoke the tool correctly (e.g., what rankType=1 vs 3 means, or what is being ranked).

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 0% across 8 parameters, and the description contributes nothing: it never explains date, region, rankType (enum 1/2/3), videoRankField (enum 1/2), productCategoryId, or createdByAi. The enum values are meaningless to an agent without explanation.

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 says only that it returns 'normalized public ecommerce research data,' which is a generic restatement of the whole family of tools and never mentions TikTok, videos, or ranking. Only the tool name and title convey what the tool actually does, so the description itself adds no differentiating information against the many sibling *_video_* and *_rank* tools.

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 guidance on when to use this tool versus alternatives such as nexscope_tiktok_video_search, nexscope_tiktok_video_analytics, or nexscope_data_kd_video_rank. Neither inclusion criteria, exclusions, nor prerequisites (e.g., date/region requirements) are stated.

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