User Showcase

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

Goes beyond annotations by disclosing that the call may consume paid API credits, that confirm=true is mandatory, and that the read-like POST does not publish to social platforms. The last point is useful given readOnlyHint=false, which could otherwise mislead an agent into thinking this mutates data. It still doesn't describe rate limits or failure behavior.

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 core purpose is stated first, followed by return shape and then two operational notes. Four compact sentences with little waste, though 'Just send the query params in the body' is slightly loose phrasing that overlaps with the pagination sentence.

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?

No output schema exists, yet the description still sketches the return payload (array of product objects with title, price, images, shop details), and it covers the credit/confirm precondition. Minor gaps remain around the account credential parameter and the practical limits of non-US regions, though the latter is documented in the schema.

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 coverage is 100%, so the baseline is 3, but the description adds real value for two parameters: it explains the cursor pagination workaround (POST fallback) and states the confirm=true requirement, both of which the schema only asserts without motivation. The region and account params get no additional description treatment.

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?

Names a specific verb (fetches) and a precise resource (products in a TikTok user's public showcase), with a clarifying gloss ('the products a creator promotes on their profile'). This scope is distinguishable from sibling shop tools like tiktok_shop_shop_products and tiktok_shop_product_details, which operate on shops rather than creator profile showcases.

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?

Offers practical invocation advice ('Use POST request if pagination is cutting off too early. Just send the query params in the body.') and a hard precondition (confirm=true), but never states when to prefer this tool over the shop or profile siblings, nor any when-not conditions. Usage is implied rather than articulated.

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