List best-selling in-stock public products (most sold first). Danh sách sản phẩm BÁN CHẠY còn hàng (đã bán nhiều nhất trước). Chỉ trả field công khai (giá VND + số đã bán). Dùng để tư vấn "hot/được mua nhiều".
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10, max 20). | |
| keyword | No | Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn). | |
| category_id | No | Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool returns only public fields (VND price and sold count), filters to in-stock products, and sorts by units sold. It does not discuss authentication, errors, or pagination beyond the schema's limit parameter, but covers the most relevant behavioral constraints.
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 compact and front-loaded with the core behavior. The bilingual Vietnamese section repeats some English content but adds the useful output-field and usage context, so the repetition is not wholly redundant.
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?
Given no output schema and no annotations, the description does enough by explaining the sort order, stock/public filter, returned fields, and intended use case, while the schema documents all optional parameters. It could be marginally richer by contrasting with similar siblings, but it is reasonably complete for a simple list tool.
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%, with all three parameters already documented (limit default/max, keyword, category_id). The description does not add significant parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
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 a specific verb and resource: 'List best-selling in-stock public products (most sold first)'. This sharply differentiates it from siblings like latest_products or recommend_products by specifying the sorting criterion, stock status, and public visibility.
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 says it is used to advise on 'hot/highly purchased' products, giving clear context for when to choose it. It does not explicitly mention when not to use it or name alternatives, so it stops short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Product discovery tools such as best_sellers, latest_products, recommend_products, and similar_products have related listing purposes and could be confused, though descriptions clarify sorting and filtering criteria. Social-check tools also overlap: check_live_facebook, deep_inspect, and check_health_bulk can all verify Facebook accounts. Most tools are distinct, but the boundaries are not always crisp.
The dominant convention is snake_case verb_noun, e.g. buy_product, search_products, list_categories, check_order_status. A few names deviate, such as best_sellers, latest_products, similar_products, how_to_start, and deep_inspect, but they are still readable and predictable.
With 19 tools, the set falls into the 16-25 heavy range and could be trimmed: there are nine product-listing/search/recommend tools and three overlapping social-check tools. The count is not extreme, and the combined commerce-plus-verification scope is covered, but it feels heavier than necessary.
The core commerce workflow is complete: discover products, quote, confirm purchase, check order status, and view balance. Minor gaps include no order-history tool, no cancellation tool, and no actual top-up execution, but these are workaroundable for the stated shop purpose.