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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavioral context: missing/null fields are left unchanged and monetary values keep their original unit and runtime type. That is useful data-handling detail an agent would otherwise not know. It stops short of saying what happens on an unknown ID or what the core/channel sections contain.

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 compact sentences, no filler. The field inventory is front-loaded and the caveats about nulls and monetary units follow immediately. Every clause carries information.

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's field list does meaningful work toward describing the return payload, which is the main gap a detail tool faces. However it leaves the `include` sections unexplained and says nothing about behavior for invalid or missing shop IDs, so an agent still lacks pieces needed to call it confidently.

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 id, country, and include are already fully documented with examples, an enum, and a regex pattern. The description adds no parameter-level meaning beyond the field list, so the baseline of 3 applies. It notably says nothing about what the `include` sections (core, channel) actually add.

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 sentence 'Provider business records for TikTok Shop Detail' restates the tool name rather than stating a specific verb+resource (e.g. 'fetch a single TikTok shop's profile by ID'). The field list (id, seller_id, shop_name, region, shop_rating, shop_total_gmv) does signal the shape of the returned record, which lifts it above pure tautology. It never distinguishes itself from siblings such as nexscope_chuhaijiang_tiktok_shop_search 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?

There is no statement of when to use this tool versus the many sibling shop tools (shop_search, shop_rankings_*, shop_related_*). Nothing says it requires a known shop ID, so the agent must infer from the schema that this is a lookup-by-ID operation. Usage is only implied by the name and params.

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