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

Annotations are sparse (readOnlyHint=false, openWorldHint=true), so the description does real work by enumerating the payload: multi-period sales/GMV windows, live sales, promoting videos and creators, views, price, rating, review count, commission rate, and delisted/fully-managed status. It does not describe cost, rate limits, or error behavior, and the read-only framing ("query") sits slightly at odds with readOnlyHint=false, though that hint is a common conservative default for external-API-backed data tools rather than a direct contradiction.

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 first two sentences are dense and front-loaded with the useful facts, but roughly half the text is a keyword-stuffed trigger list repeating "TikTok product detail", "TikTok GMV", and "TikTok live sales" multiple times, which adds no selection signal.

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 a two-parameter batch read tool with full schema coverage and no output schema, the description covers inputs, batch limits (in schema), and the shape of returned data, which is what an agent needs to invoke it. The remaining gap is routing against the crowded set of sibling TikTok product tools.

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 coverage is 100% and both parameters are documented in-schema, including the max-1000 cap and the fact that productUrls are parsed and merged into productIds. The description only restates that IDs or URLs are accepted, adding little beyond the schema — the baseline 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 opening sentence gives a specific verb and resource ("Batch query TikTok product detail data") and enumerates the returned metrics, and "Supports batch retrieval by product ID or TikTok Shop product URL" pins down the input mode. It distinguishes itself from single-product siblings only implicitly via "batch" — it never names nexscope_chuhaijiang_tiktok_product_detail or nexscope_tiktok_product_analytics as the non-batch alternatives.

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?

The trigger list and the closing sentence give broad when-to-use conditions ("whenever their need involves batch retrieval of detailed TikTok product sales ... by product ID or product URL"). However, it offers no when-not guidance, no exclusions, and no routing to the many sibling TikTok product tools (single product detail, product search, product analytics, shop product detail), so the agent must infer the boundary from the word "batch".

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