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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's real contribution is cost and region behavior. It does disclose that lookups consume credits and that repeats may re-purchase data, but the cost claim is self-contradictory ('at least 10 Nexscope credits' versus '1 credit per request' near the end), which is materially misleading for a metered 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 text is bloated with duplication and pasted API-doc artifacts: the US-only constraint appears three times, the 'Get the details of a TikTok Shop Product' sentence appears twice, and fragments like 'View Pricing ... Examples are not guaranteed prices' are noise. The genuinely useful content (return shape, cost, region behavior) is buried rather than front-loaded.

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 no output schema, the description does the heavy lifting by enumerating the response structure down to fields like skus[].stock, gtin_type/gtin_code nullability, shop_rating, and related_videos. What keeps it short of complete is the unresolved credit-cost conflict and the absence of any error-behavior note beyond 'may return bad_request'.

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%, and the schema already documents both `url` and `region`, including the US-reliability caveat. The description only restates that lookup is by URL and repeats the US-only constraint, adding little syntax or meaning beyond the structured fields; 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 description opens with a specific verb and resource: 'Fetches full details for a specific US TikTok Shop product by its URL,' and enumerates the returned sections (product_info, skus, shop_info, related_videos). It does not distinguish itself from adjacent siblings such as social_tiktok_shop_products, social_tiktok_shop_search, or nexscope_tiktok_shop_product_detail, so an agent must infer the single-product-by-URL vs. list/search split.

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?

Usage context is implied rather than stated: you supply a product URL, and the endpoint is US-only. The repeated caveat that 'Repeated requests may purchase data again' is a useful operational warning, but there is no explicit when-to-use/when-not guidance and no routing to a sibling for non-US products or for list/search style lookups.

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