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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no indication of result shape, ranking window semantics, rate limits, or what 'promoted' data includes. 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 economy — a single fragment that merely repeats the title. Nothing is front-loaded because there is nothing substantive to front-load.

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 several near-identical sibling ranking tools, the description should explain what the endpoint ranks and how results differ from the products and shop variants. It leaves that entirely unaddressed; only the annotations and schema prevent the definition from being unusable.

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% with 8 documented parameters, so the schema carries all parameter semantics (date format YYYYMMDD, country code, granularity values, pageSize 1–20). The description adds no interpretation, but per the baseline rule a 3 is appropriate when the schema does the heavy lifting.

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 restatement of the tool name and title: 'TikTok Commerce Intelligence CJ: sellers/rankings/most promoted API.' It conveys the domain (TikTok sellers) and the ranking type, but supplies no verb or explanation of what 'most promoted' actually returns or measures. An agent gets no help distinguishing this from nexscope_data_cj_products_rankings_most_promoted or nexscope_data_cj_sellers_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 when-to-use guidance, no prerequisites, and no mention of the closely named sibling rankings tools (products_rankings_most_promoted, sellers_rankings_top_selling). The agent must infer selection 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.