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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so 'fixed read-only provider path' merely restates them without adding context. Nothing is said about ranking semantics, date handling, pagination behavior, or data freshness.

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 a single short sentence, but brevity here reflects under-specification rather than efficiency; there is no useful front-loaded information beyond a generic claim.

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 ranking tool with 4 required params, cryptic enum codes, no output schema, and no annotation-level detail needs the description to explain semantics. The description explains nothing, so an agent cannot confidently call it.

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 four parameters are bare enums whose meanings are opaque: rankType 1/2/3, videoRankField 1/2, and createdByAi 'true'/'false'. The description supplies no parameter meaning at all, leaving the agent unable to choose values correctly.

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 never states the resource being ranked (TikTok videos) or that this returns a ranked list; the only signal comes from the tool name and title. 'Returns normalized public ecommerce research data' is generic boilerplate that could apply to hundreds of sibling 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?

No indication of when to use this versus nexscope_tiktok_video_search, nexscope_tiktok_video_analytics, nexscope_data_kd_video_rank, or the other ranking tools. There are no exclusions, prerequisites, or alternative references anywhere in the text.

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