TikTok Shop Search

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

Annotations already cover readOnly/openWorld/destructive, so the description's value-add is noting the request is routed through the Decodo Web Scraping API and returns Markdown rather than raw HTML. That extra context on output format is useful. It does not discuss rate limits or result caps, which would be a 5.

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 short sentences with the purpose and the return type front-loaded, followed by a docs link. Every element earns its place; the only slight cost is the docs URL, which isn't actionable information for the model.

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?

There is no output schema, and the description compensates by stating results are returned as Markdown. Combined with full schema coverage and annotations, an agent has enough to call the tool correctly; only the result shape (item fields) is left undefined.

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 (query, country, jsRender, deviceType) are already documented, including the enum for deviceType. The description adds nothing about parameter semantics, so baseline 3 applies.

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 (search TikTok Shop for a keyword) plus the return format (Markdown), so an agent knows exactly what it does. It stops short of naming how it differs from siblings like tiktok_shop_product or tiktok_shop_url, which is the only gap.

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?

"Use it to find products sold on TikTok Shop in a given country" is implied guidance but never states when not to use it or which sibling to prefer for a direct product/URL lookup. The alternative tool routing is left to inference.

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