temu_site_list

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

With no annotations, the description carries the full burden. It discloses matching behavior ('精确匹配，不按语言、币种或相似名称猜测'), ambiguity handling ('无匹配或多个匹配时请用户确认'), and how to interpret the returned currency. It does not explicitly state read-only or pagination, but the core behavioral traits are well covered.

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?

The description is dense but every sentence earns its place: purpose, usage conditions, matching logic, and result usage. It's front-loaded with the primary purpose and avoids redundancy despite its length.

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 single-parameter lookup tool with an output schema, the description fully covers when to call, what to pass, how to handle ambiguity, and how to consume the result. It leaves no significant gaps for the agent to invoke correctly.

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?

The schema has one parameter with no description (0% coverage). The description compensates by explaining the parameter's meaning: 'country 使用用户给出的中文名或英文名做精确匹配' and that it is optional with a default fallback to site ID 48. This adds essential semantics beyond the schema.

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 clearly states the tool's function with a specific verb ('实时查询' - real-time query) and resources (Temu country sites, site IDs, internal region IDs, currency). It also distinguishes itself from sibling search tools by being a site lookup, and even provides explicit exclusions (US site, no site specified), reinforcing its unique purpose.

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?

The description explicitly states when to call: '仅当用户明确指定美国以外的国家或地区时调用' and when not to call: '未指定站点或指定美国站时直接让业务工具使用默认站点 ID 48'. It also instructs how to use the result in other tools (商品、图搜、店铺、类目、关键词或评论查询), providing clear context and alternatives.

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