get_item_description
Reads one item’s product-detail card — the panel that opens behind the product photo in the delivery app: ingredients, portion size, flavour, preparation method, whether it contains caffeine, and so on. Every row is written by the merchant. Read-only, mutates nothing.get_shop_menu tells you a dish exists and what it costs. This tool tells you what it actually is.
Typical scenarios:
- Dietary restrictions and allergies: the user says “no beef” or “I’m allergic to nuts” — check the ingredients before ordering.
- Portion size: “how big is this cup”, “is it enough for two”.
- Flavour and preparation: how spicy, how it is cooked, served hot or iced.
- Caffeine, sugar and other health questions: coffee and tea shops commonly fill these in.
Every merchant fills in different rows. The row label (
label) is chosen by the merchant and is not a fixed schema: a coffee shop may return “是否含咖啡因” (contains caffeine), “咖啡豆烘培程度” (roast level) and “咖啡豆品种” (bean variety), while a noodle shop returns “荤素” (meat/vegetarian), “凉热” (hot/cold) and “制作方法” (preparation). Render whatever comes back, as it comes back — never assume a given row is present, and never read values off a fixed list of labels.Parameters
This tool is item-level and takes no
sku_id. One call covers an item however many skus it has. If a row genuinely differs per sku, the values are merged into a single row — see “Portion size on multi-sku items” below.Response
An empty
details is a real answer, not an error. It means this merchant wrote no description for this item. Tell the user so; do not retry.One row overlaps
get_shop_menu’s description. The “商品描述” (product description) row carries the same text as that item’s description in the menu, so this tool alone gives you the complete write-up. If you have already shown the menu blurb, you can skip this row to avoid repeating yourself.
