TikTok Shop URL

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely useful context: it returns the page's raw HTML and warns the payload is often several hundred KB. It does not discuss rate limits, auth, or failure modes, but the key behavioral trait (large raw payload) is disclosed.

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 tightly written sentences, front-loaded with the action and resource, followed by routing guidance to siblings. Every clause carries information; the size warning earns its place.

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 correctly compensates by stating the return value is raw HTML. Combined with annotations and full schema coverage, an agent has enough to call it correctly; only minor gaps (e.g. dynamic content handling) remain.

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 both url and jsRender are already documented in the schema. The description adds no syntax or format detail beyond that, so the 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?

States a specific verb (Fetch) and resource (any TikTok Shop page by URL) and explicitly names the two sibling tools it complements (tiktok_shop_search and tiktok_shop_product). An agent can immediately tell this is the generic URL-based fallback scraper.

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?

Clearly states when to use it: for TikTok Shop pages the search and product tools do not cover, such as shop or category URLs. It names the alternatives but does not explicitly state when NOT to use it (e.g. for single product pages where the dedicated tool is better).

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