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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower; the description still adds useful traits — credit cost, pagination via cursor, market scope, and the shape of returned fields (price, rating, review, sales counts). The only weakness is the unresolved tension between 'US market' and the region parameter.

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?

Three short sentences, front-loaded with the action and followed by output shape, scope, and cost. Every sentence carries information; nothing is padded.

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 naming the returned fields and stating page-by-page behavior plus cost. It is close to complete for a search tool, with the region/market discrepancy the main remaining ambiguity.

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 80% and most parameters (query, count, cursor, region) are self-documented; the description adds only 'page by page', which lightly reinforces cursor/count semantics. It says nothing about cache_max_age or how region interacts with the stated US-market scope.

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 and resource ('Search TikTok Shop') and clarifies the returned entity is products, page by page. It implicitly separates itself from tiktok_product/tiktok_productReviews (lookup by id vs. query search) but never names a sibling, so an agent must infer the boundary.

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?

'Costs 1 credit' and the pagination hint give practical context, but there is no explicit when-to-use guidance and no mention of alternatives such as tiktok_shopProducts or tiktok_product. Additionally, the description asserts 'US market' while the schema exposes a region parameter for US, GB, ID, leaving the agent unsure which governs.

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