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

Annotations only supply readOnlyHint=false and openWorldHint=true; the description adds nothing about what the ranking is based on, the time window semantics of `date`/`granularity`, pagination limits, or result ordering. With readOnlyHint=false on what is evidently a read query, a clarifying sentence about the non-mutating, paginated nature would have been especially valuable.

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 with no padding, but it is under-specified rather than concise — nothing is front-loaded except a restatement of the name. Every word is technically 'used', yet none of it is informative.

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 an 8-parameter, 3-required ranking endpoint with no output schema, the description should at minimum say what the result set contains and what it is ranked by. It leaves both wholly unexplained, so the agent must guess at return shape and ranking basis.

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%, so all eight parameters are already documented and the baseline of 3 applies. The description adds no meaning beyond the schema — for instance, it does not explain how `granularity` interacts with `date` or what `shopType` codes 1–4 mean.

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 a near-verbatim restatement of the tool name and title ("TikTok Commerce Intelligence CJ: sellers/rankings/top selling API"), which amounts to a path fragment rather than a stated purpose. An agent can infer it returns a ranking of sellers by sales, but nothing distinguishes it from siblings like nexscope_data_cj_sellers_rankings_most_promoted or nexscope_data_cj_products_rankings_top_selling.

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 ranking versus the most_promoted, new_arrivals, search, or detail siblings, and no note on required inputs or context. The agent must infer usage purely 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.