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

Annotations only supply readOnlyHint=false and openWorldHint=true, so they carry little behavioral meaning for a search operation. The description does add useful output semantics: which row fields exist, that missing/null fields are left unchanged, and that monetary values keep their original unit and runtime type. It says nothing about cost, rate limits, result caps, or why this read-shaped tool is flagged non-read-only.

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, tightly sized with no padding. The first sentence is boilerplate that restates the title, but the second sentence (field list plus null/unit semantics) 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?

For a 13-parameter, no-output-schema tool, the field enumeration effectively substitutes for a missing output schema, and null/unit behavior is disclosed. The remaining gap is usage context, not return values: nothing tells an agent how this differs from sibling shop search, detail, and ranking tools.

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 every one of the 13 parameters (country enum, keyword, category, min/max GMV, rating and sold filters, sort pattern, pageSize cap of 10) is already documented in the schema. The description adds no parameter-level meaning beyond the listed row fields that happen to correspond to the metric filters, 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?

The description identifies the resource as TikTok Shop search records and enumerates the returned shop fields (shop_name, region, shop_rating, GMV, etc.), which lets an agent infer it searches shops. But the opening sentence, 'Provider business records for TikTok Shop Search,' largely restates the tool name rather than stating a verb and scope, and it never says what is being searched over (keyword, category, country).

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?

There is no statement of when to use this instead of the many adjacent TikTok shop tools (nexscope_chuhaijiang_tiktok_shop_detail, nexscope_chuhaijiang_tiktok_shop_rankings_top_selling, nexscope_tiktok_shop_analytics). No prerequisites, no exclusions, no alternative routing are given.

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