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

Annotations already provide readOnlyHint/openWorldHint, so the safety profile is covered. The description adds useful behavioral context: it returns a list and mentions pagination. However, the phrase 'use cursor when paginated' is not matched by any `cursor` parameter in the schema, and the actual `page` parameter is never acknowledged, creating a slight transparency gap.

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 one tight sentence that front-loads the core purpose and immediately signals return type and pagination. There is no filler or repetition of the title.

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 simple read-only list operation with well-documented parameters, the description is mostly adequate. However, it omits the practical need to provide either `url` or `productId` despite zero required params, and the pagination reference conflicts with the schema's `page` parameter. The lack of an output schema is partially compensated by 'Returns a list'.

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 explains `url`, `page`, `region`, and `productId`. The description adds almost nothing beyond 'by product id', and it does not clarify the relationship or trade-off between `url` and `productId`. Baseline 3 is 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 states a clear verb ('List'), resource ('buyer reviews'), and scope ('for a TikTok Shop product by product id'). It is distinguishable from siblings like tiktok_product_get, though it does not explicitly name or differentiate from alternatives. The slight ambiguity between 'by product id' and supporting a `url` param keeps it from a 5.

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 is given about when to prefer this tool over other TikTok Shop or product-related tools, nor are any exclusions or alternatives mentioned. The intended use is only implied: when one needs buyer reviews for a product. There is no explicit routing signal.

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