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

No annotations are provided, so the description carries the full burden. It does disclose safety ('Read-only') and the shape of the useful return fields (shop_url/user_id), but says nothing about pagination behavior, result limits, or rate/authorization constraints for a 20-item-capped query.

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?

Effectively one dense sentence; the core action is front-loaded and the routing caveat follows. The parenthetical mixing Chinese and English is compact but slightly harder to parse quickly.

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 2-parameter, no-output-schema search tool, the description covers purpose, safety, return fields, and the key alternative route. Missing only page_size/pagination guidance, which is minor given the small parameter set.

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 0%, so the description must compensate. It implicitly defines 'query' as a keyword, but 'page_size' (default 10, max 20) is never addressed, leaving paging semantics to the raw schema only.

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?

Names a specific verb and resource ('search Taobao shops by keyword') and immediately scopes the result to shop discovery (shop_url/user_id), which separates it from the product-oriented siblings like cps_smart_search and cps_jd_goods_search.

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?

Explicitly routes purchase/link-following intent to cps_smart_search's buy_url and notes that the legacy shop.get interface no longer returns click_url, so the agent knows what this tool is not for. It stops short of stating broader when-to-use conditions (e.g., when to prefer shop search over item search for discovery).

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