How to use the Restaurant Menu Description Generator.
Menu descriptions should make the dish appealing through accurate ingredients and preparation. Do not add dietary, sourcing or allergen claims unless the kitchen has verified them.
Make the workflow fit your task.
Lead with the dish's actual ingredients and preparation, using sensory wording that the kitchen can support. Keep the description concise and verify any dietary, sourcing or allergen labels separately. Compare the text with the current recipe before publishing.
- What you provide
- Verified dish ingredients and preparation.
- What you get
- Appetizing factual menu descriptions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Dish is roasted carrots with yogurt sauce and toasted cumin; no dietary certification is supplied.
Completed example
Roasted carrots with a cool yogurt sauce and toasted cumin. Keep the description grounded in the supplied dish and confirm the kitchen's allergen information before adding labels.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a menu description call a dish gluten-free based only on its name?
No. Ingredients, preparation and cross-contact need appropriate verification before making that claim.
Why does appealing menu copy create wrong expectations?
It may add ingredients, cooking methods or portions absent from the recipe. Keep descriptive details tied to confirmed facts.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑