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

Beyond the readOnly and openWorld annotations, the description discloses that calls go through a residential proxy, cost $0.002 USDC per successful call via x402 on Base/Solana/Arc, and failed calls are not charged. It also describes output scope: about 10 products plus a few reviews and the category tree.

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 description is front-loaded with the core purpose and output fields, followed by input and payment details. It is dense but every part is relevant to calling or budgeting the tool, though the single long sentence could be slightly easier to scan.

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?

Given the presence of an output schema and annotations, the description supplies everything else an agent needs: output fields, input formats, proxy usage, and payment terms. No critical context for correct invocation is missing.

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 both parameters are already well documented. The description reinforces the URL/slug/id input format but adds little semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 clearly states that this tool returns TikTok Shop (US) category-page products, specifying fields like title, price, rating, reviews, and the category tree. It is a specific resource, though it does not explicitly contrast itself with sibling TikTok tools such as social_tiktok or social_tiktok_comments.

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?

It explains the accepted input format (category URL from shop.tiktok.com/us/c/... or slug and id), which helps callers invoke it. However, it provides no explicit guidance on when to use this tool instead of related TikTok or e-commerce sibling tools, nor any exclusions.

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