Menu Description Copy is a Claude AI skill — appetite-driven descriptions calibrated to cuisine style, venue tone, and dish character.
A restaurant in east London rewrote its entire menu in an afternoon. Not the dishes — just the descriptions. The lamb shoulder that had sat at twelve percent order rate for six months became the second most-ordered main within two weeks. Same dish, same price, same position on the menu. Different twelve words underneath the name. The chef had been describing what was in the dish. The rewrite described what it was like to eat it.
Menu copy is the only piece of hospitality writing that has a direct, measurable effect on revenue per cover. Every other piece of brand writing — the website, the social posts, the email newsletter — operates at a distance from the transaction. The menu is read at the moment of decision, by someone who is already seated, already committed to spending money, actively looking for reasons to order. It's the highest-conversion sales surface a restaurant has, and most of them treat it as an administrative document.
Generic AI makes this worse, not better. Ask vanilla Claude to write a menu description and you get a list of components, possibly with an adjective or two attached to the most prominent ones. "Pan-seared duck breast with cherry reduction, dauphinoise potatoes, and seasonal greens." That sentence contains accurate information and zero appetite appeal. It answers the question "what's in this dish?" rather than the question the diner is actually asking: "is this the one I want?"
What Generic Menu Copy Gets Wrong
The failure of generic AI menu copy isn't factual inaccuracy — it's the wrong job entirely. Menu descriptions do two things, in this order: they create desire for the dish, and they justify the choice. A description that lists components does the second job while skipping the first. It gives the diner information about what they're buying but never makes them want to buy it.
Desire in a menu description is created through sensory language, flavour hierarchy, and texture contrast — the specific combination of words that makes a reader's mouth respond before they've consciously decided anything. "Slow-braised" signals tenderness and depth. "Crisp-edged" signals texture contrast. "Bright" used about a sauce signals acidity and freshness against something rich. These are precise tools, not decorative ones. Generic AI produces adjectives the way a spell-checker produces suggestions: statistically plausible, contextually inert.
A menu description's first job is not to inform — it's to create appetite. The information is necessary; the appetite is what makes someone choose this dish over the one above it on the page.
Venue tone compounds the problem. The description that works for a relaxed neighbourhood bistro is wrong for a tasting menu restaurant, and both are wrong for a wedding reception caterer's evening buffet card. The casual bistro wants warmth and directness — "sticky, slow-cooked short rib, chips, béarnaise" has earned its place on that menu. The tasting menu wants precision and restraint — every word carries weight because there are very few of them. The wedding caterer needs approachable elegance: descriptions that read well on a printed card held by someone in formal wear who doesn't want to feel like they're decoding a Michelin guide. Generic AI produces one register and applies it everywhere.
That gap is exactly what the Menu Description Copy skill for Claude was built to close.
What Cuisine and Tone Calibration Changes
The Menu Description Copy skill takes three inputs before writing anything: the dish and its key components, the cuisine style and cooking approach, and the venue or occasion tone. Those three inputs determine vocabulary register, description length, flavour emphasis, and whether the copy leads with technique, provenance, texture, or occasion.
A Japanese-influenced dish at a high-end restaurant gets different treatment from a Jamaican jerk dish at a street food market, even if the structural components of the descriptions are similar. The former calls for restraint and precision — the description does less work because it trusts the cuisine's reputation to carry some of the appetite signal. The latter calls for heat, energy, and directness — the description needs to communicate the experience of eating it, not just the method of preparation. Calibrating to cuisine style isn't aesthetics. It's matching the description to the register the dish and its diner already exist in.
The best menu descriptions don't describe the dish. They describe the experience of eating it — and let the diner imagine themselves there.
Occasion tone changes the length and formality more than anything else. A printed wedding menu card reads in a quiet moment — guests have time, the setting rewards considered language, and the description is part of the event's atmosphere rather than a sales tool competing for attention. A pub gastropub menu reads in a noisy room while someone is also talking to you — it needs to land in three seconds or it hasn't landed at all. Both contexts require good copy. They require completely different kinds of good copy. The skill knows the difference because the three-question interview establishes it before a word is written.
How the Menu Description Copy Skill Works
Three inputs, then a research pass for current tone conventions in your cuisine category, then up to a full menu section of descriptions — with a length variant for each dish so you have options for different menu formats.
Ingredient List vs Appetite Copy
Same dish, same components. One described by vanilla AI, one by the skill. The test: which one makes you want to order it?
Contains: dairy. May contain gluten.
gf available · d
The left description is accurate and generic — it could have been written for any lamb dish at any restaurant. The right description does several things the left doesn't: "gives way at the touch of a spoon" creates a specific tactile anticipation that "slow-cooked until tender" doesn't. "Been going since this morning" signals genuine commitment to the dish without claiming anything unprovable. "Enough butter to be honest about it" has the register of the venue — self-aware, confident, not pretending the mashed potato is a health food. The allergen format on the right is cleaner and faster to read in a fine dining context. None of that required knowing more about the dish — it required knowing what register to write it in and what appetite signals to lead with.
Who Gets the Most from This Skill
Restaurant and café owners writing or refreshing a menu without a dedicated copywriter. Private chefs and caterers producing menu cards for events where the description is part of the presentation. Wedding planners and venue operators writing reception menus where tone has to match the occasion as much as the food.
The skill is most valuable when you have good food and underdescribed copy — when the dish is better than its menu description suggests. It's also well-suited to new menus where every dish needs copy from scratch, seasonal updates where a section needs to be rewritten quickly, and event catering where the menu card is a designed object and the copy needs to match the aesthetic register of the event.
It's less suited to menus that need to integrate tightly with a highly distinctive existing brand voice built over years — the copy will be good, but it may need closer editing to match a voice the skill hasn't been given time to internalise. For most hospitality contexts, the output is ready to use or needs a single pass of personalisation rather than a structural rewrite.
The Output You Walk Away With
For each dish: two descriptions at different lengths, with the appetite signals calibrated to your cuisine and venue tier, allergens flagged in the format that matches your context, and a note on the flavour hierarchy the description leads with and why. Run the skill across a full menu section and you receive consistent tone across all dishes — no jarring register shifts between one description that sounds like a food blog and the next that sounds like a product label.
From download to copy-ready: open the skill in Claude, give it the dish details and venue context, receive descriptions for the full section. The editing left is the chef's knowledge — the specific provenance claim only you can make, the cooking detail that differentiates your version from the generic version of the dish, the one ingredient note that rewards a curious diner. That layer is yours. The skill handles the appetite architecture that makes it worth reading in the first place.
The menu is the last piece of hospitality writing most restaurant owners think about and the one that sits in front of every paying guest at the highest-stakes moment of their visit. The food earns the return visit. The menu description is what gets the dish ordered in the first place — and a dish that doesn't get ordered, regardless of how good it is, is a dish that doesn't exist from a revenue perspective. That twelve words matters more than most people in hospitality give it credit for.
The next piece most people tackle from here is a eulogy that honours the person, not the occasion. If you're working across the full Wedding workflow, the Wedding bundle covers everything in one place.
Put this to work: the Menu Description Copy skill for Claude turns everything above into one guided workflow you run in a normal Claude chat. Not ready to buy? Start with a free Claude skill and see how it works first.