Product Details

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

Adds substantial context beyond annotations: it warns that the call consumes paid API credits, mandates confirm=true, discloses the hard US-only regional limitation, and explicitly resolves the apparent tension of readOnlyHint=false by noting the read-like POST does not publish to social platforms. Annotations alone would leave the cost and regional constraints invisible.

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?

Front-loads purpose, then the return shape, then constraints; every sentence carries information, and the return-field enumeration is warranted since no output schema exists. The first sentence is long and comma-heavy, slightly reducing scanability.

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 fully carries the burden of describing return contents, including the null case for gtin and the nested structure of skus and product_detail_review, and it covers cost, confirmation, and region caveats. Nothing an agent needs to invoke it correctly 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 url, region, account, and confirm are already documented; baseline is 3. The description reinforces the region restriction and the confirm requirement, but adds no syntax or format detail beyond the schema text (e.g., accepted URL forms).

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 and resource ('Fetches full details for a specific US TikTok Shop product by its URL') and enumerates the exact payload (product_base, skus, product_detail_review, shop_info, related_videos). The depth of detail (stock counts, affiliate videos) distinguishes it from tiktok_shop_shop_products and tiktok_shop_product_reviews without the agent opening either schema.

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?

Gives concrete conditions: US region only, confirm=true required for the credit-consuming call. It does not explicitly name alternatives (e.g., tiktok_shop_product_reviews for review-only needs, tiktok_shop_shop_products for catalog listing), so routing is inferred rather than stated.

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