TikTok Shop Product

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: the request is proxied through the Decodo Web Scraping API under the 'tiktok_shop_product' target, the response is Markdown (important since there is no output schema), and a docs link is provided. It still says nothing about credits, rate limits, or failure modes.

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 tight sentences with the action and return format front-loaded, followed by a single docs URL. Nothing is redundant with the title, and every clause carries usable information.

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 four-parameter read-only scraper with a fully described schema and no output schema, the description covers what it does, how to invoke it, and what comes back (Markdown). Only edge-case behavior — failures, geo-restriction effects of the country parameter, cost — is absent.

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 all four parameters (country, jsRender, deviceType, product_id) are already documented at the schema level. The description only reinforces product_id and says nothing about country/jsRender/deviceType, so per the baseline rule this sits at 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?

The description gives a specific verb and resource ('Fetch a TikTok Shop product page by product ID') and states that the result comes back as Markdown via the Decodo Web Scraping API. The clause 'Use it when you know a TikTok Shop product ID' implicitly separates it from URL-based sibling tiktok_shop_url, though no sibling is named explicitly.

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 states a clear trigger ('when you know a TikTok Shop product ID and need its price, seller or description'), which is enough to route an agent away from search-type siblings. It stops short of naming alternatives or stating when not to use it (e.g., when you only have a URL, use tiktok_shop_url).

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