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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context — that missing/null fields are returned unchanged and that monetary values keep their original unit and runtime type — which is useful for interpreting results, but it says nothing about pagination limits, result caps, or latency.

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 sentences, no filler beyond the somewhat awkward "Provider business records" opener. The enumerated field list is dense but each item earns its place by telling the agent what rows look like; front-loading the operation name before the field inventory is reasonable.

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 13-parameter search tool with no output schema, the description does cover the returned row shape, which is the biggest gap it could fill. However, it omits pagination behavior, the maximum reachable result depth, and any guidance on how filter parameters combine — leaving an agent under-informed for a filter-heavy search endpoint.

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% across all 13 parameters, so the schema already documents each field, including the country enum and the sort pattern. The description adds no parameter-level meaning (e.g., how `sellerType` or `category` values are sourced), 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?

"Provider business records for TikTok Shop Search" restates the tool name more than it explains the operation; an agent must infer from the field list (shop_name, shop_rating, shop_gmv_for_last_7_days) that this returns a paged list of TikTok shops. It never explicitly says "search shops by keyword/country/filters," and gives no contrast with siblings like nexscope_chuhaijiang_tiktok_shop_detail or nexscope_chuhaijiang_tiktok_shop_rankings_top_selling.

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?

No statement of when to use this tool versus the several shop-related siblings (shop_detail, shop_rankings_top_selling, shop_rankings_most_promoted, shop_related_creators). The only usage signal is the required `country` parameter, which the schema already conveys.

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