Menu Description Copy is a Claude AI skill — appetite-first descriptions calibrated to cuisine, venue tone, and dish character.
Pick up any restaurant menu and read the descriptions with this question in mind: does this copy make me want to order the dish, or does it just tell me what's in it? Most menus fail that test on most dishes. "Pan-seared salmon with lemon butter sauce, wilted spinach, and new potatoes" is a complete, accurate sentence that creates zero appetite. It's the food equivalent of a car listing that says "vehicle with engine, four wheels, and seats." Factually correct. Completely unmotivating.
Menu copy occupies a unique position in hospitality: it's the only written touchpoint between a restaurant and a guest that happens at the exact moment of purchase. The website generated interest. The reservation confirmed intent. The atmosphere set the mood. The menu description is what determines whether the kitchen sells the dish it wants to sell, whether the guest leaves satisfied with their choice, and whether the margin on that cover is what it should be. Most restaurants treat it as a labelling exercise. The ones that treat it as a sales tool notice the difference in covers.
The gap isn't between good writing and bad writing. It's between descriptions that create a sensory anticipation of eating the dish and descriptions that convey information about it. Those are different jobs, and most menu copy — including most AI-generated menu copy — defaults to the informational one because it's easier to produce and harder to evaluate until you're looking at order data.
The Three Things Appetite-Driven Copy Does
Effective menu copy operates on three levels simultaneously: it creates sensory anticipation, it establishes a flavour hierarchy, and it justifies the price point. Each level serves a different psychological function in the ordering decision. Generic AI copy addresses the third level passably and ignores the first two almost entirely.
Sensory anticipation is the physical response a description triggers before the food arrives. It's the reason "slow-braised until it collapses" lands differently than "tender braised meat" even though both descriptions are accurate. The first creates a specific tactile image. The second describes a category. Sensory anticipation is created by technique words that carry textural meaning, by contrast language that implies complexity, and by specificity that makes the reader feel they already know what this dish is like to eat.
Flavour hierarchy tells the diner which element is the experience and which elements support it. A dish that leads with "charred aubergine, tahini, pomegranate, flatbread" puts all four components at the same level and gives the diner no map through the eating experience. The same dish written as "smoke-charred aubergine, the flesh gone silky, tahini pooled underneath, sharp pomegranate cutting through — flatbread for the rest" establishes the aubergine as the point, the tahini as the foundation, the pomegranate as the tension, and the flatbread as the satisfying resolution. That's a description that makes someone commit.
Price justification is implicit in the language register and the specificity of the description. A twenty-eight pound main course needs copy that makes the ingredient quality and technique feel commensurate with the price. "Slow-cooked short rib with truffle jus" does this work. "Beef with sauce" does not, even if the dish is identical. The description doesn't need to mention the price — it needs to make the price feel obvious.
A diner reading a menu is not evaluating nutritional content or ingredient lists. They're imagining eating the dish. Menu copy that helps them imagine it vividly — texture, contrast, the first bite — wins the ordering decision against copy that only describes what's present.
That gap is exactly what the Menu Description Copy skill for Claude was built to close.
The Words That Create Appetite vs the Ones That Don't
Not all adjectives are equal in menu copy. Quality adjectives — "delicious," "flavourful," "hearty," "succulent" — are common in generic AI output and almost useless in practice. They make a positive claim without creating any sensory experience. A diner's brain processes "delicious" as a marketing assertion and moves on. It processes "charred at the edges, giving way in the centre" as a physical experience and stays there.
The most effective menu vocabulary falls into a small number of categories: technique words that carry textural implication, contrast words that signal complexity, specificity words that signal quality provenance, and process words that signal effort and care. Here's how they divide:
- Delicious — subjective, unverifiable
- Flavourful — circular descriptor
- Tender — category, not sensation
- Succulent — overused, now invisible
- Hearty — vague quantity signal
- Seasonal — expected, not differentiating
- Fresh — baseline expectation, not a selling point
- Charred — smoke, crust, contrast
- Slow-braised — depth, time, collapse
- Bright — acid, lift, contrast to richness
- Silky — specific texture, not category
- Cold-smoked — technique, specificity
- Sun-dried — concentration, intensity
- Wood-fired — heat, char, provenance
The strong column works because each word carries embedded sensory information — it tells the diner something specific about what they're about to experience rather than asserting a quality level. Generic AI menu copy defaults heavily to the weak column because those words are statistically prevalent in training data from menus that were themselves poorly written. The skill's live research identifies the current vocabulary conventions in your specific cuisine category and venue tier, and writes from the strong column by default.
How Copy Requirements Differ Across Venue Types
The same dish requires fundamentally different copy depending on where it's being served and who is reading the menu. Register, length, vocabulary formality, and the balance between technique and accessibility all shift with venue context. Generic AI applies one register to all of them.
| Venue type | Reading context | Copy register | Length target | What the copy leads with |
|---|---|---|---|---|
| Fine dining / tasting menu | Quiet, unhurried, anticipatory. Guest has chosen the venue deliberately. | Restrained precision. Every word carries weight. No quality adjectives — technique and provenance do the work. | 15–25 words. Brevity signals confidence. | Technique or provenance. The quality of the ingredient is assumed; the method is what's worth saying. |
| Casual bistro / neighbourhood restaurant | Relaxed but still choosing quickly. Ambient noise, distraction present. | Warm and direct. Can carry personality — a hint of the kitchen's voice. Some texture language, a clear flavour signal. | 20–35 words. Enough to sell, not enough to lose. | The dish's dominant flavour character. What makes this version worth ordering over the version they've had before. |
| Wedding / formal reception menu card | Slow, ceremonial read. Guest is in formal setting; description is part of the occasion's atmosphere. | Approachable elegance. Warm but polished. Avoids technical culinary jargon; accessible to non-foodie guests without feeling dumbed down. | 25–45 words. Occasion warrants slightly more; the card is a keepsake as much as an ordering tool. | The celebratory quality of the dish. Language that makes the food feel special-occasion worthy rather than instructional. |
| Event buffet / catering label | Standing, time-pressured, competing visually with other dishes. | Clear and immediate. No flourishes. Lead with the dominant flavour and cooking method; signal allergens prominently. | 8–15 words maximum. Read in two seconds or not at all. | The recognisable identity of the dish. The description confirms what the diner thinks they're looking at, then adds one appetite signal. |
| Street food / market stall | Noisy, competitive, impulse-driven. The description competes with adjacent stalls for attention. | High energy, direct, no hedging. Attitude is a legitimate copy element here — the personality of the food should come through. | 10–20 words. Must land at reading speed while walking. | Heat, boldness, or the thing that makes this dish specific to this stall. The copy should feel like it was written by someone who eats this food with enthusiasm. |
The Menu Description Copy skill takes venue type as one of its three inputs precisely because copy that works in one context actively undermines another. Fine dining restraint on a street food board reads as cold and inaccessible. Street food energy on a wedding menu card reads as casual at an event that isn't. Getting the register right is not a stylistic preference — it's matching the copy to the context in which the decision is being made.
Why Flavour Hierarchy Determines What Gets Ordered
When a menu lists components without establishing which element is the experience and which are the supporting cast, the diner has to do interpretive work to understand what they're ordering. Most diners don't do that work consciously — they just feel vaguely uncertain about the dish and move to the next one. Flavour hierarchy resolves that uncertainty before it becomes a skip.
Establishing hierarchy is a structural choice before it's a vocabulary choice. The component named first carries the most weight — the diner's mental model of the dish is anchored to the first noun they read. A description that opens with the protein establishes a protein-led dish. A description that opens with a sauce or a technique signals that the sauce or technique is the point. "Slow-braised ox cheek, celeriac purée, gremolata" reads as a meat dish with supporting elements. "Celeriac purée, slow-braised ox cheek resting on top, sharp gremolata cutting through" reads as a composed dish where the relationship between elements is the experience. Same components; the ordered first noun tells a completely different story about what you're buying.
The first noun in a menu description anchors the whole dish in the diner's imagination. Everything after it is understood in relation to it.
Generic AI doesn't make this structural decision deliberately — it defaults to listing components in a conventional order (protein, starch, vegetable, sauce) that was established for kitchen organisation purposes, not appetite creation ones. The Menu Description Copy skill makes the hierarchy decision based on what's most compelling about the specific dish and what the venue's cuisine tradition establishes as the expected leading element. For a Japanese-influenced dish, technique often leads. For a Middle Eastern dish, the spice profile or the cooking method often leads. For a British seasonal dish, provenance often leads. These aren't rules — they're the conventions that the cuisine's audience already has expectations about.
Questions About Menu Copy and Food Writing
The menu is the only marketing material a restaurant produces that its customers read at the exact moment they decide to spend money. Every other channel — social media, Google reviews, the website — operates at a distance from the transaction. The menu operates inside it. Copy that creates appetite at that moment isn't a nice-to-have refinement to an already-working system. It's the mechanism by which good food becomes ordered food, and ordered food is the only kind that generates revenue.
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.