Menu descriptions that sell without adjectives

"Delicious, mouth-watering, perfectly cooked steak, served with our famous hand-cut chips." Every word in that description is trying to sell, and almost none of it tells the guest anything. Which cut of steak? How is it cooked? What makes the chips different from anyone else's? The guest who reads it knows only that they are being sold to.

Compare: "Rump steak, chargrilled, bone marrow butter, triple-cooked chips." Eight words, no adjectives that claim anything, and the guest knows exactly what they will eat and why it might be good. That is what menu descriptions are for.

This guide covers what good menu descriptions do, why around eight words usually works, what to include and what to leave out, the words that make guests trust a menu less, and how descriptions work alongside menu photography, menu design and the team's own words. Every figure in it is an example.

A menu description has three jobs. It helps the guest choose, by telling them what the dish is and what makes it worth ordering. It sets expectations, so the plate that arrives matches what the guest imagined. And it carries information the guest needs, such as a key ingredient that matters for a dietary need or an allergy.

It is not there to impress. A description that reads like an advertisement makes guests suspicious, because they have read too many advertisements. A description that reads like a clear, specific account of the dish makes guests trust the kitchen, because it sounds like the kitchen knows exactly what it is doing.

Good menu copy is therefore closer to a label than to a poem: precise, concrete and true.

There is no rule, but many good menus describe their dishes in somewhere around six to twelve words. That is enough to name the main ingredient, the cooking method and the one or two things that make the dish distinctive, and short enough to read at a glance.

Longer descriptions have their place on a tasting menu or a menu with few dishes, where guests have time to read and want detail. On a menu of twenty dishes, long descriptions crowd the page and slow the guest down. Many guests skim them and miss the point.

Shorter is not always better either. A dish described only as "chicken" tells the guest nothing about what makes it worth ordering. The aim is the fewest words that let the guest picture the plate.

Most good descriptions contain three things.

Add anything the guest needs to know to choose safely or happily: a spicy element, a dish that comes rare, a main that comes without sides. Leave out anything that does not help the choice.

Much of what appears in menu descriptions does not help the guest at all.

Leave out adjectives that only claim quality, such as "delicious" or "perfect". Leave out the obvious: a salad is fresh, a soup is hot, a steak is cooked. Leave out long stories about suppliers and farms, unless the venue is built around them and guests want them; a short credit, such as a farm's name, can be enough. Leave out every ingredient: the guest does not need the full recipe, only the parts that make the dish.

Each word you cut makes the remaining words stronger. A description of five well-chosen words is more persuasive than one of twenty where the good ones are buried.

The most useful words in a menu description are nouns and verbs: what the dish is made of and what was done to it. "Lamb shoulder, slow-cooked for seven hours, with anchovy and rosemary" uses nouns and a verb to tell the guest everything. It needs no adjective to sell it.

Adjectives that describe something real can help: "crisp", "smoked", "charred", "sour", "sticky". They tell the guest about texture and flavour. Adjectives that only express an opinion, such as "amazing", "divine" or "irresistible", tell the guest nothing except that the venue thinks highly of itself.

A good test is to ask of each adjective: could the guest disagree with it after eating? "Smoked" can be checked; "divine" cannot. Keep the ones that can be checked.

A few words appear on so many menus, and promise so much, that they now make many guests trust a menu less.

None of these is forbidden. A dish genuinely known across the city can be called famous. But each one claims something the guest cannot judge until the plate arrives, and a menu full of claims reads like a sales pitch. Describe the dish instead, and let the guest decide whether it is delicious.

Menu descriptions work best in plain language. Short words, short phrases, familiar terms. Guests read menus in noisy rooms, in dim light, while talking to their friends, and every unnecessary word or obscure term makes the menu harder to use.

Writing in plain English does not mean dull writing. It means choosing the clearest word for each thing: "braised" rather than "lovingly slow-simmered", "with" rather than "accompanied by", "served on" rather than "presented atop".

Read each description aloud. If it sounds like something a server would say naturally at the table, it is probably right. If it sounds like a brochure, cut it back.

Every word in a description must be true. If it says local, the ingredient comes from nearby. If it says homemade, it is made in the kitchen. If it says fresh, it has not been frozen. If it names a breed, a region or a farm, that is what is on the plate.

Accuracy is a matter of trust and, in many places, of law. Consumer protection rules in the UK and elsewhere expect descriptions of food to be accurate and not misleading, and a menu that claims more than it delivers can be challenged by guests and by inspectors.

Accuracy also has to survive change. When a supplier changes, a dish is simplified or an ingredient is substituted, the description must change too. A menu that was accurate in spring can be quietly wrong by autumn if nobody checks.

Descriptions can help guests with allergies and dietary needs, as long as they are not mistaken for full allergen information. Mentioning a key ingredient that guests might not expect, such as anchovy in a dressing, nuts in a crust or cream in a sauce, helps guests notice it before they order.

But a description is not an allergen list, and guests should not have to rely on it. Keep full allergen information in its own record and its own place on the menu, with a clear note asking guests to tell their server about allergies. Our guide to dietary labels guests can trust on a menu covers how labels and descriptions work together.

When a description changes, check whether the allergen information needs to change too. A new garnish may bring a new allergen.

The name and the description do different jobs. The name is what guests say when they order and what the kitchen sees on the ticket; the description tells guests what it is.

Keep names short and clear. "Lamb shoulder" is a good name; "The Shepherd's Dream" is not, unless the description makes the dish plain. Playful names can suit a casual venue, but they should always be followed by a description that says exactly what the dish is.

Names also appear on the kitchen ticket and the bill. A name that is clear to guests, cooks and servers alike avoids confusion at every step.

Menus often use terms from other languages or from the kitchen: confit, beurre blanc, gochujang, za'atar, al dente. Some guests know them; many do not. A term guests do not understand is a barrier to ordering.

Use such terms where they are the right word, but help the guest. "Duck leg confit, slow-cooked in its own fat" explains the term in the same line. "Za'atar flatbread, with thyme, sumac and sesame" tells the guest what to expect.

Servers can help too, but a guest who has to ask what every second word means will often choose the dish they already understand, which may not be the one the kitchen most wants to sell.

Menu copy and menu design depend on each other. Descriptions of a consistent length make a page look calm and ordered; descriptions that vary from three words to forty make it look messy. Our guide to menu layout: one page, two columns or a folder covers how the page itself affects reading.

Set a style and apply it to every dish: the same order of information, the same punctuation, the same way of naming the main ingredient and the method. A menu where every description follows the same pattern is easier to read, because the guest learns the pattern in the first few lines.

Keep the style in a short note for whoever writes descriptions in future, so new dishes match the menu rather than following whoever wrote them.

Menu photography and descriptions do different jobs. A photograph shows what a dish looks like; a description explains what it is and what makes it good. Each works best when it does its own job.

A photograph of a dish makes long description unnecessary. On a digital menu where each dish has a photograph, the description can be shorter, focusing on what the photograph cannot show: the cooking method, the flavour, the key ingredient. On a printed menu without photographs, the description carries more of the load.

Make sure the photograph and the words agree. A description that mentions a garnish missing from the photograph, or a photograph of a dish that has since changed, undermines both.

On a phone, guests often see a dish's name and the first line of its description in a list, and tap to see more. That changes how descriptions should be written.

Put the most important words first. On a phone, "Rump steak, chargrilled, bone marrow butter" works even if the end of the line is cut off; "A generous and beautifully seasoned cut of our finest" gives the guest nothing before the cut. The opening words should carry the dish.

A digital menu can also hold more detail behind a tap: the full list of ingredients, the allergens, a photograph. Use that space for what guests may want but not every guest needs, and keep the first line short and clear.

Descriptions support the team's suggestions. A server who recommends the lamb can point to a description that already makes it appealing; a description that mentions a side or a sauce gives the server an easy way to suggest it.

But descriptions should not do the server's job. "Ask your server about our wine pairings" on every line clutters the page. A short, clear description and a server who knows the dish work better together than a description that tries to sell everything. Our guide to upselling that does not sound like selling covers the server's side.

Where a dish is better with something extra, a description can say so plainly: "best with the peppercorn sauce". That is information, not pressure.

Specials and set menus need descriptions too, and they are often written in a hurry on the day. A special chalked on a board as "fish of the day" tells guests nothing; "Sea bream, grilled whole, salsa verde" tells them everything and sells far better.

Write each special in the same style as the rest of the menu, and make sure the server can describe it in the same words. For a set menu, describe each course as you would a dish on the main menu, and say clearly what the set price includes, so guests are never surprised by a supplement or a side that costs extra. A set menu with clear, honest descriptions is easy to choose, which is most of its appeal.

If you want to know whether a new description works, test it. Change the description of one dish and compare how often it sells over a few weeks with how it sold before, in similar weeks with nothing else changed.

Descriptions are rarely the only reason a dish sells or does not, so treat the results with care. But a dish that starts selling noticeably more after its description was rewritten, with nothing else changed, is good evidence. So is a dish whose questions from guests fall away once the description is clearer.

Ask servers, too. They hear guests' questions about every dish, and a description that keeps generating the same question needs rewriting.

Rewriting every description at once is a good exercise at a menu change. Work dish by dish with the chef, who knows what makes each one distinctive, and a server, who knows what guests ask.

For each dish, agree the main ingredient, the method and the one or two distinctive things. Write the description from those, in the agreed style, and cut every word that does not earn its place. Then read the whole menu aloud, section by section, to check it flows and the descriptions feel consistent.

Check every description for accuracy against the dish as it is cooked today, and against the allergen record. A rewrite is also a chance to catch descriptions that drifted from the plate.

An invented brasserie's mains read like this: "Our delicious, perfectly cooked chicken, served with seasonal vegetables and a rich, indulgent sauce." Guests often ask servers what the sauce is and what the vegetables are, and the chicken sells modestly.

The brasserie rewrites every main in its new style: main ingredient, method, distinctive elements. The chicken becomes "Roast chicken breast, tarragon cream sauce, roasted carrots and greens". The fish becomes "Hake, brown butter, capers, crushed new potatoes". Each description fits on one line, with no adjective that only claims quality.

Over the following weeks, servers report fewer questions about the mains, and guests who order the chicken say it was exactly what they expected. The chicken's sales rise a little. The menu reads more calmly, and several guests remark that it is easy to choose from.

In servearound, each dish's description is written once and used wherever the dish appears: on the menu guests open from a table's QR code, on the venue's menu page, on digital menu boards and in print designs. A dish that sits on several menus shares one description, so a rewrite reaches every menu at once. Each dish can also carry an ingredients list, shown on the menu card and searchable, and photographs.

On the guest menu, a dish's allergen and dietary tags sit in their own sections, apart from the description, so the copy can stay short. Print designs say when a dish has been renamed since they were printed. The menu report shows how each dish sells before and after a description changes, and from the digital menu, how often guests opened a dish against how often they ordered it. See the menus module.

Usually around six to twelve words: enough to name the main ingredient, the method and what makes the dish distinctive.

The main ingredient, the cooking method where it matters, the one or two things that make the dish distinctive, and anything the guest needs to know to choose.

Adjectives that only claim quality, such as delicious or perfect, tell the guest nothing. Adjectives that describe something real, such as smoked or crisp, can help.

Claims they cannot check, such as delicious, famous, authentic and perfect, especially when used throughout the menu.

Yes. Every word should be true of the plate, and consumer protection rules in many places expect food descriptions not to mislead.

They can mention key ingredients guests might not expect, but full allergen information belongs in its own record and its own place.

The photograph shows the dish; the description explains it. With a photograph, the description can be shorter and focus on what the picture cannot show.

Put the most important words first, so the first line works even if it is cut off, and keep extra detail behind a tap.

Change one dish's description, compare its sales over similar weeks before and after, and ask servers whether guests still ask the same questions.

Menu descriptions sell best when they describe rather than claim. Around eight words is often enough: the main ingredient, the method and the one or two things that make the dish distinctive. Use nouns and verbs, keep adjectives that describe something real, and drop the words that only claim quality, which make guests trust a menu less.

Write in plain English, keep every word true and up to date, mention unexpected key ingredients without replacing allergen information, and explain unfamiliar terms in the same line. Keep one style across the menu, let photographs and words do their own jobs, put the important words first for phones, and test rewrites against sales and servers' experience.