Product Reviews

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

Description adds useful context beyond annotations: 'Potentially consumes paid API credits; requires confirm=true', and clarifies read-like POST requests do not publish to social platforms. This clarifies credit/billing cost and idempotency-like behavior not fully in annotations (annotations only say readOnlyHint=false and idempotentHint=false). It does not explain failure modes or retry semantics, but the credit warning is a strong piece of behavioral transparency.

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?

Two sentences: first covers the main behavior and return shape; second flags a critical side-effect (credits/confirm) and clarifies it's not a social post. Efficient and front-loaded. Slightly dense return-field list but no fluff.

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 6-param tool with no output schema, the description is reasonably complete for identification, return shape, and pagination. However, it does not cover region reliability constraints (which are only in the schema), does not describe error behavior, and does not explain account selection semantics. Adequate but with clear gaps for a paid, region-sensitive tool.

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 handles naming and basic meaning. Description still adds value by clarifying required-ish inputs ('by URL or product_id') and emphasizing pagination via 'page', plus implies region reliability indirectly (schema covers that fully). Marginal added detail beyond schema, above the baseline 3.

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?

States a specific verb (Fetches) and resource (customer reviews for a TikTok Shop product), and identifies the two identifier inputs (URL or product_id). Reads clearly and is distinguishable from siblings like tiktok_comments or tiktok_shop_product_details.

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?

Provides some actionable guidance by stating 'Paginate with page', and notes a product URL or id is needed as an identifier. But does not say when this tool should be preferred over similar siblings (e.g. tiktok_shop_product_details), nor does it state when/how to choose url vs product_id beyond the schema, nor caveats around which region to use.

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