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 mention of authentication, region/currency sensitivity, rate limits, or what a failed lookup returns. It is also unclear why a 'detail' read is flagged as non-read-only, and the description does nothing to resolve that ambiguity.

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 fragment with no filler, but it is also pure duplication of the title and endpoint path, so no sentence earns its place. Brevity here reflects under-specification rather than economy.

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?

A five-parameter data tool with no output schema and uninformative annotations needs the description to explain what a product detail record contains, what the region/dateRange parameters change, and how results differ from sibling tools. None of that is present, so an agent cannot call this confidently.

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 five parameters (including productId format hints and region/currency/language/dateRange examples) are already documented in the schema. The description contributes zero additional parameter meaning, which meets the baseline 3 under high coverage but no higher.

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: 'TikTok Intelligence KD: product/detail API.' It implies retrieving details for a TikTok product, but 'product/detail API' is essentially the tool name and endpoint path rather than a stated verb+resource outcome. It does not distinguish itself from the many near-identical siblings such as nexscope_chuhaijiang_tiktok_product_detail or nexscope_data_tiktok_shop_product_detail.

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, no exclusions, and no pointer to any alternative. With dozens of TikTok product-related siblings (product search, analytics, rankings, shop product detail), an agent has no basis to choose this tool over them.

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