List newest in-stock public products (recently added first). Danh sách sản phẩm MỚI còn hàng (thêm gần đây nhất trước). Chỉ trả field công khai (giá VND). Dùng để tư vấn "hàng mới về".
| 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 of behavioral disclosure. It provides useful context: results are limited to in-stock public products, sorted newest first, and only public fields such as VND price are returned. It does not discuss auth, rate limits, or empty-result behavior, but these are less critical for a simple list operation.
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 core English sentence is front-loaded and clear, but the Vietnamese line largely repeats the same information and only adds one new piece: the intended consultation use case. This bilingual duplication keeps it from being fully concise.
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 low-complexity tool with three optional parameters and no output schema, the description covers the essential behavior: ordering, availability, public-field restriction, and intended use case. It does not describe the exact result shape, but the public-field note and schema-provided parameters are sufficient for correct invocation.
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%; limit, keyword, and category_id are already described in the input schema. The description adds no notable parameter-specific details beyond reinforcing the public/newest scope, 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 states a specific verb ('List'), a specific resource ('newest in-stock public products'), and an explicit ordering ('recently added first'). This clearly distinguishes it from siblings like best_sellers or search_products by focusing on new arrivals with public data only.
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 a clear use case: 'Dùng để tư vấn hàng mới về' (use for advising about new arrivals). It does not explicitly mention when not to use the tool or name alternative tools, so it lacks exclusions, but the context for its intended purpose is clear.
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.