What to cook: how to check a generated recipe
The "What to cook" tool is a text recipe generator. You fill in four fields: ingredients and quantities, preferences and restrictions, number of portions and available time. After pressing Generate you get one text result in a separate panel, which can be copied or downloaded as a regular TXT file. No style settings, sliders or detail levels are available in the interface. The purpose of this article is to show how to independently check how accurate, complete and suitable for real cooking the proposed recipe is. We will analyze a fictional example: potatoes, carrots, onions, lentils and tomatoes, dinner for two in 30 minutes.
Open tool: Recipe generator ↗What exactly the tool generates and what to check first
"What to cook" outputs text with a recipe, not an image and not a step-by-step video. It is important to understand: the result is only a verbal description that you read and interpret yourself. Therefore the first check always concerns correspondence with the input data. Open the original fields and compare: are all the ingredients you listed mentioned in the recipe, were any products added that you do not have, and do the quantities match?
The second check is structure. A good result usually contains a list of ingredients with quantities, a sequence of actions and at least an approximate time. If the text is one solid paragraph without stages, it can still be used, but the risk of missing a step increases. Evaluate not the beauty of the formulations, but completeness: is it clear what and in what order to do?
The third check is realism. The model may suggest baking for 40 minutes although you specified 30 minutes for everything. Or it may write "boil lentils until done" without clarifying that dry lentils require pre-soaking and long cooking. Such discrepancies — the main signal that the result needs to be adapted manually.
Input: ingredients — potatoes, carrots, onions, lentils, tomatoes; restrictions — no meat; portions — 2; time — 30 minutes.
Checking accuracy: ingredients, quantities and restrictions
Accuracy starts with quantities. If you specified "4 medium potatoes", and the recipe says "potatoes to taste", that is loss of information. Compare each position: is the quantity preserved, was it doubled without reason, is there enough liquid for the specified volume of grain or legumes? For lentils especially it is important, canned or dry: this affects both time and water amount.
Restrictions are checked separately. If you wrote "no meat", the text must not contain meat products, broths or gelatin. If "gluten-free" is specified, check soy sauce, pasta and spices. The model may not know about hidden allergen sources, so the final decision is always yours. The tool is not a medical or dietary advisor.
Portions and time are also part of accuracy. A recipe for two must not require a six-liter pot without warning. If time is stated as 30 minutes, check whether chopping, frying and stewing fit into it. Often the generator gives an optimistic estimate, and it is worth increasing it by 10–15 minutes as a reserve.
Check: the recipe specifies canned lentils — this matches 30 minutes. If it were dry lentils, the time would have to be recalculated.
Completeness: what is missing in a good answer
A complete recipe answers the questions: what to prepare in advance, in what cookware to cook, how to understand readiness and what to do if a product is missing. If the text contains only a list of actions without explanations, this is not an error of the tool, but a reason to ask a clarifying question or supplement yourself.
Pay attention to missing basic steps: washing vegetables, chopping, heating oil, adding salt. Models sometimes consider this obvious and omit it. For a beginner such omissions are critical. Check whether it is stated when to add spices and how to regulate the heat.
Separately evaluate whether there is an option for substitution. If you run out of onions or tomatoes, it is useful to know what can replace them. A good result either proposes an alternative, or at least does not make the dish impossible without the missing component. If there is no substitution, this is a limitation, not a defect.
Incomplete answer: "fry the vegetables and add lentils". Complete: "heat oil, fry onions 3 minutes, add carrots, then potatoes and lentils, pour water and stew 15 minutes".
Suitability: can this really be cooked
Suitability is the most practical criterion. Ask yourself three questions: do I have all the cookware, do I have enough time and will it turn out edible with my skills? If the recipe requires a blender and you do not have one, the result is unsuitable without adaptation. If an oven is needed and you were counting on the stove, this is also important to notice before starting.
Check the sequence of operations for conflicts. For example, simultaneously boiling lentils and stewing vegetables on one burner may be inconvenient. A good recipe either uses one cookware or honestly warns about parallel work. Evaluate whether you will have to run between stages.
Finally, evaluate the flavor logic. A combination of potatoes, carrots, onions, lentils and tomatoes — a working base: it is the foundation for a ragout or soup. If the model suggests adding, for example, sugar to a tomato vegetable mix, it is acceptable, but it must be explained. Strange combinations without explanation — a reason to doubt.
Suitable option: one pot or deep skillet, 30 minutes, no oven and no blender.
How to check the result step by step
Step one: read the whole text without starting to cook. Step two: compare ingredients and quantities with what you entered. Step three: mark all places where it says "to taste" or "until done" and decide whether you understand what that means. Step four: check time and cookware. Step five: mentally run through the process from beginning to end.
If you get stuck at some step, formulate a clarification and generate again. The tool does not store history and does not have a comparison mode, so save successful variants manually — by copying or downloading TXT. This is the only way to return to a good result.
Remember the service limitations: fields have character limits, answers may contain errors, and queue and availability change. Do not treat one result as final. Two or three runs with slightly different formulations often give a more complete picture.
Checklist: ingredients match, restrictions observed, portions correct, time realistic, cookware available, steps understandable.
Typical errors and how to spot them
The first frequent error — ignoring the type of product. Canned and dry lentils, fresh and dried tomatoes, young and old carrots cook differently. If the recipe does not specify this, clarify yourself or re-formulate the request.
The second error — unrealistic time. The model may add up the stage times incorrectly. Compare: chopping vegetables — 5–7 minutes, frying — 5–8, stewing — 15–20. If the sum exceeds the stated 30 minutes, plan more.
The third error — hidden allergens and controversial additives. Check the composition of sauces, broths and spices. The tool does not give safety guarantees for health, so with allergies and medical restrictions consult a specialist.
Error: "stew 10 minutes" for dry lentils. Fix: use canned lentils or increase time to 60–90 minutes after soaking.
Tool limitations and honest expectations
"What to cook" is a text generator, not a culinary encyclopedia and not a personal dietitian. It does not check product freshness, does not calculate calories with guarantee and does not take your medical indicators into account. The result always requires your check.
The interface is intentionally simple: four fields, Generate button, one result. No saving, integrations, batch processing and export to DOCX or PDF. Available: copying and downloading TXT. This means that organizing recipes is your task.
Do not expect the tool to replace experience. It is useful as a source of ideas and a draft that you adapt to your kitchen, cookware and taste. Evaluate its result by accuracy, completeness and suitability — and then even an imperfect answer becomes a good starting point.
Realistic expectation: a recipe draft in 30 seconds, which you refine 5 minutes to your conditions.
Checking the "What to cook" result boils down to three questions: does the recipe match your ingredients and restrictions, is it complete enough, and can it really be cooked in the stated time. On the fictional example with potatoes, carrots, onions, lentils and tomatoes it is visible that key risks — type of legumes, optimistic time and missing steps. Use a checklist, save successful variants in TXT and remember: the tool gives a draft, and the decision and responsibility remain with you.
Open tool: Recipe generator ↗Interface translations are machine-assisted and may need refinement.