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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds no behavioral context at all – no pagination behavior (pageSize max 10, page min 1), no freshness, no auth or quota notes. It does not contradict the annotations, but it carries none of the burden that the thin annotation set leaves open.

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 filler, but it also contains no information beyond the title, so brevity comes at the cost of utility rather than from disciplined editing.

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 four parameters, no output schema, and only the thinnest annotations, the description must explain what 'related videos' returns and how pagination works. It supplies none of that, so an agent cannot confidently invoke it or interpret results.

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 the schema already documents id (Store ID), country, page and pageSize. The description adds no additional meaning beyond the schema, but the baseline of 3 applies 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 restates the title verbatim ('TikTok Commerce Intelligence CJ: sellers/related videos API') without a verb or any explanation of what data is returned. An agent can infer it lists videos related to a seller, but nothing distinguishes it from siblings like nexscope_data_cj_sellers_related_products or nexscope_data_cj_sellers_related_creators.

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 guidance on when to use this tool, what prerequisites exist, or which sibling to prefer for adjacent needs. The many sibling 'related_*' tools make this omission costly.

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