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

Annotations only supply readOnlyHint=false and openWorldHint=true, so the description must add context, and it does: missing/null fields stay unchanged and monetary values keep their original unit and runtime type — useful for downstream parsing. However, it says nothing about empty-result behavior, whether all known fields are always present, or the cost/latency of the external data call behind openWorldHint.

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 tight sentences, no repetition or padding, with the value-formatting caveats front-loaded in the second sentence. The opening clause is somewhat formulaic boilerplate, which keeps it from a 5.

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 does list known row fields, giving partial return-value coverage. But it never explains what the optional `include` sections (core, channel) change in the response, nor how a missing shop or an invalid id behaves — gaps an agent would want for a 3-param external lookup.

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 100%, so id, country, and include are fully documented in the schema (including the enum and the core/channel pattern). The description adds no parameter-level meaning beyond that, 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 Detail" largely restates the tool name/title rather than stating a specific verb+resource. The row-field list (id, seller_id, shop_name, region, shop_rating, shop_total_gmv) hints that this returns a single shop's record, but nothing distinguishes it from siblings like nexscope_chuhaijiang_tiktok_shop_search or the shop_rankings_* tools.

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 when-to-use guidance at all: no mention of when a shop detail lookup is appropriate vs. nexscope_chuhaijiang_tiktok_shop_search, shop_rankings_top_selling, or shop_related_* tools. The agent must infer usage purely from the name and required id/country params.

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