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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot convey: the per-call price of ¥0.1, that only successful calls are billed, and that failures or empty results are automatically refunded — this materially affects how eagerly an agent should call it.

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 purpose and return contents, then the use case, then the billing terms — no filler. The billing sentence is not padding because cost-per-call changes invocation behavior, though the use-case sentence is terse enough to read as a fragment.

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 usefully enumerates the returned fields, and it covers billing behavior. However, for a four-parameter tool where nothing is marked required, an agent still has no guidance on whether shop_id, seller_id, or both are needed, nor on pagination behavior beyond the schema's default of 1.

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 parameter is documented in the schema itself, which sets the baseline at 3. The description adds nothing about the parameters, and notably leaves unexplained the ambiguity of having both shop_id and seller_id present with zero required parameters, so it does not compensate for the terse one-word schema descriptions.

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 states a specific verb and resource (search a Taobao shop's product listing) and even names the return fields (product ID, title, price, sales volume). The platform is disambiguated by the name and text, but it never contrasts itself with the analogous jd_shop_search / douyin_shop_search or with taobao_item_get, so sibling differentiation is left to the name alone.

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?

It gives one concrete usage scenario (competitor shop inventory checks and on-sale structure analysis), which implies when to reach for it. There is no guidance on when not to use it, no mention of alternatives such as taobao_item_get for a single item, and no prerequisite information about needing shop_id versus seller_id.

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