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

Annotations already declare readOnly=true and destructive=false, so safety is covered, and the description adds genuinely useful context: the returned fields without an output schema, plus a warning that repeated requests may purchase data again. However, it self-contradicts on cost ('at least 10 Nexscope credits' vs. '1 credit per request'), which actively undermines the credit guidance an agent needs for cost-aware invocation.

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 first three sentences are well-formed and front-loaded, but they are followed by pasted marketing/pricing boilerplate ('Scrape TikTok Shop Products from a search!', 'View Pricing', 'Actual supplier units are reported per request. Examples are not guaranteed prices.'). There is duplicated and contradictory pricing text that does not serve agent invocation.

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 simple read-only search with no output schema, listing the returned fields is the right compensating move, and the region reliability caveat is present. But the credit cost is stated twice with conflicting numbers and there is no mention of result limits or how many items per page, leaving real gaps for a 3-param, cost-bearing tool.

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?

With 100% schema description coverage, the schema already documents `query`, `page`, and `region`, including the enum and the non-US reliability caveat. The description's only addition is restating pagination and region filtering, which adds no syntax or format detail beyond the schema. 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 opening sentence states a specific verb and resource: search TikTok Shop for products matching a keyword. This usefully disambiguates the ambiguous tool name 'shop_search', which could otherwise read as 'search for shops.' It does not differentiate this from the many sibling TikTok product-search tools (e.g. social_tiktok_shop_products, nexscope_tiktok_product_search), so it stops short of a 5.

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 offers partial operational guidance ('Paginate with `page`; filter by region') and the schema notes that non-US regions are unreliable, but it gives no when-to-use or when-not-to-use criteria, no alternative tools, and no guidance on result volume or query construction. Usage is implied rather than directed.

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