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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds nothing beyond them — no note about what the ranking measures, whether results are cached, or what the time window does. It neither confirms nor clarifies the unusual readOnlyHint=false on what is ostensibly a rankings read call.

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 entirely redundant with the title, so brevity does not earn its place. It is under-specification rather than conciseness, and there is no front-loaded statement of purpose to orient the agent.

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 parameters, 3 required, no output schema, and a mutation-flagged annotation, the tool needs real explanation of the ranking metric and result shape. The description provides none, leaving the agent to guess from the name alone.

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 every one of the 8 parameters (date, country, granularity, page, pageSize, sort, category, shopType) is already documented in the input schema. The description contributes no additional meaning, so the baseline of 3 applies.

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 tool name and endpoint path ('sellers/rankings/most promoted API') without adding a verb, scope, or explanation of what a 'most promoted' seller ranking actually contains. An agent can infer the resource from the identifier, but nothing distinguishes it from nexscope_data_cj_sellers_rankings_top_selling beyond the literal words in the name.

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 statement of when to use this tool, no exclusions, and no mention of the near-identical siblings (nexscope_data_cj_sellers_rankings_top_selling, nexscope_data_cj_products_rankings_most_promoted, nexscope_chuhaijiang_tiktok_shop_rankings_most_promoted) that an agent must choose between. The description supplies zero routing information.

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