How to Write a Book Description for KDP

Your book description is not a synopsis for your editor. It is the only long-form argument on the Amazon detail page that you control before the reader hits Buy or Read sample — and most of it is hidden until they expand Read more.

This guide is a writing process for Amazon KDP descriptions: a four-beat structure that works for fiction, nonfiction, and low-content books; the constraint that your first lines do almost all the conversion work; and the claim families KDP’s own help page will not accept. When you want copy already shaped for KDP’s HTML whitelist and character budget, use the KDP Description Generator. If you already have a draft, paste it into the free KDP Listing Checker before you publish.

Not affiliated with Amazon. Length limits, HTML rules, and description restrictions below describe public KDP help-page rules. KDP can change editor behavior and help docs — confirm against the current Write a Book Description page before you ship a high-stakes listing.

The constraint that bites

Write the first two lines last — after you know what the book is for — then put them first.

On the detail page, shoppers see only the start of your description before Read more. There is no public, stable “character count before the fold” published by Amazon; the fold moves with device, font size, and layout. Treat it as a hard product constraint anyway: if the first screen does not answer what this is and who it is for, many readers never open the rest.

That is why a beautiful third paragraph about themes never rescues a vague opening. Order of work:

1. Decide the reader promise (what they get by the end of the book or session).
2. Draft the body that proves the promise (contents, stakes, differentiators).
3. Write a two-line hook that earns the expand.
4. Only then add HTML for scanability — and only tags KDP supports.

The second bite is policy, not craft: a description that “sells hard” with reviews, prices, URLs, or “buy now” language can get blocked or stripped. Several popular marketing guides still recommend leading with star quotes or testimonials. On KDP, that is a documented restriction family, not a growth hack.

The durable core: hook → promise → proof → CTA

KDP’s own advice is short: make the description simple, compelling, and professional — main idea only, a first sentence that draws the reader in, genre expectations clear, no typos. Their sketch even aims at roughly a 150-word paragraph that is easy to scan. That is a starting length, not a ceiling: the hard limit is 4,000 characters including HTML tags, per the same help page.

Turn “simple / compelling / professional” into a structure you can reuse:

hook    →  one or two lines that name the book and the reader’s itch
promise →  what they get (outcome, experience, or story shape) — not the whole plot
proof   →  specifics that make the promise believable (contents, stakes, credentials)
CTA     →  a soft close that invites the next click without promo language

Beat	Job on the detail page	Failure mode
Hook	Earn Read more (and signal genre / activity type)	Clever line that could describe any book
Promise	Tell them what they walk away with	Plot dump or chapter list with no “why buy”
Proof	Make the promise concrete	Superlatives (“best,” “#1”) with nothing behind them
CTA	Move them to sample, cart, or series	“Buy now,” prices, URLs, review requests

This structure survives rate-table and UI changes. Character budgets and exact HTML tags can shift; who the description is for and what claims are allowed stay the load-bearing parts.

Hook (above the fold)

The hook is not a tagline contest. It is product copy:

• Name the category in plain language — large-print word search, enemies-to-lovers romantasy, first-time homebuyer guide — so the right reader self-selects in one glance.
• Name the tension or outcome — one conflict for fiction; one main takeaway for nonfiction; one activity promise for puzzle / low-content books.
• Stay short enough that the full hook fits before the fold on a phone. If you need three sentences, the first sentence still has to work alone.

KDP explicitly wants a first sentence that draws readers in and sets genre expectations. Bold that line in the editor if it helps scan — but budget the tags: every <b> pair counts toward the 4,000-character limit. Full tag list and budgeting live in Which HTML Tags KDP Actually Supports.

Promise (what they get)

After the hook, one short block answers: If I buy this, what happens for me?

• Fiction: protagonist, situation, central conflict, tone — without the ending. KDP forbids spoiler information in the description for BMVD listings; treat “no spoilers” as a hard rule, not optional courtesy.
• Nonfiction: the problem the reader has, the approach you take, and the transformation or skill they leave with.
• Puzzle / activity / low-content: count and type of pages or puzzles, skill level or age band, extras that matter (answer key, solutions in the back, large print, one puzzle per page). Vague “hours of fun” is weaker than “100 medium-difficulty mazes with solutions.”

Do not confuse promise with keyword stuffing. KDP’s restriction list includes “any keywords or book tags phrases” as something the description cannot accept. Natural genre and topic words that a human would say are fine; a comma-separated SEO dump is not a description.

Proof (why believe you)

Proof is specific and checkable:

• What’s inside (sections, puzzle counts, tools, recipes, frameworks) — especially for nonfiction and activity books.
• Who it’s for and who it is not (beginners vs advanced; kids vs adults).
• Series context if it matters (“Book 2 of … — reads alone”).
• Author authority that is real — relevant experience, prior titles in the same niche. Fiction readers often care more about story than credentials; nonfiction readers care more about why they should trust the method.

What is not proof on a KDP description:

• Customer review quotes and “readers say…” blocks (restricted).
• Invented awards, “#1 bestseller” claims you cannot substantiate, or competitor name-dropping that misrepresents the book.
• Price, “on sale,” stock status, or alternate-order URLs (restricted).

Editorial praise and awards that are true are a gray area authors often want to force into the blurb. KDP’s restriction line is blunt on reviews, quotes, or testimonials. If you need a place for longer merchandising, that is closer to A+ Content and Author Central — which have their own guidelines — not a free pass to paste star ratings into the description field. When in doubt, put the proof in facts about the book, not third-party praise.

CTA (soft, policy-safe)

A CTA on Amazon is not a billboard. The button is already on the page. Your job is to remove the last hesitation:

• Point to the free sample / Look Inside when the book has a strong opening.
• Invite the right reader (“If you want quiet evening puzzles without tiny grids…”) without “buy now,” “add to cart,” or “order today.”
• For series, make the reading order clear so they pick the right volume.

Anything that smells like an advertisement, website URL, phone number, email, or request for customer reviews belongs off this field. KDP lists those restrictions explicitly on the Write a Book Description help page.

What KDP will not accept in a description

These are not style tips. They are the Book description restrictions from KDP’s help page. Build your draft so none of them appear:

Restricted family	What authors often try	Safer rewrite direction
Contact & web	Author site URL, email, phone, mailing address	Keep contact on Author Central / back matter where allowed
Reviews & testimonials	“Five stars,” “readers say,” pasted quotes	Specific contents and outcomes, not third-party praise
Requests for reviews	“Please leave a review if you liked it”	Remove entirely from the description
Ads & promotional material	Coupon codes, freebie funnels, watermark language	Describe the book, not the campaign
Time-sensitive info	Tour dates, “launch week only,” seminar schedules	Evergreen promise; put dates elsewhere
Price & availability	“Only $9.99,” “in stock,” “also on my site”	Let the buy box handle price; no alternate-order info
Spoilers (BMVD)	Ending reveals, twist dumps	Stakes and setup without the resolution
Unicode emojis	Decorative emoji in the blurb	Plain text and allowed HTML
Keyword / tag dumps	“Keywords: romance, billionaire, …”	Weave relevant terms into real sentences, or use the 7 boxes
Pornographic / offensive content	—	Out of scope for a conversion guide; follow content guidelines

Two related rules live next door:

• Metadata must match the book. Content guidelines apply to the product description: do not promise interior content that is not there, and do not use descriptive content meant to mislead.
• Backend keywords are a different field. Discovery phrases that will not fit the blurb belong in the seven keyword boxes, not pasted at the bottom of the description. See KDP’s keyword help and, when you fill those boxes, tools built for that job — not the description generator alone.

Fiction vs nonfiction vs low-content (same bones, different meat)

Fiction

Lead with situation + desire + obstacle. One main conflict is enough. Tone words (“wry,” “gothic,” “slow-burn”) do more work than “a fantastic novel.” Comp titles are common in trade marketing (“for fans of…”); keep them honest so the reader is not baited into the wrong book. Do not end the description with the ending.

Nonfiction

Lead with the reader’s problem, then your method, then a short map of what is inside (bullets work well here). Credentials earn trust when they are relevant (“twelve years as a classroom teacher,” “built X in production”) — not when they are a résumé dump. Promise a usable outcome; prove it with structure.

Puzzle books, journals, and other low-content

Shoppers compare count, difficulty, print readability, and extras. Your description should read like a product sheet written in full sentences:

• How many puzzles / pages / prompts
• Difficulty progression or single level
• Layout promises (one per page, large print, solutions included)
• Who it is for (age band, large-print readers, travel size — only if true)

“Hours of entertainment” without numbers loses to a competitor who states 100 large-print word searches with answer key. That is still a promise + proof structure; the hook is simply more concrete.

Worked example (illustrative)

Imagine a large-print word search book: 100 puzzles, medium difficulty, answer key in the back, one puzzle per page, aimed at adults who hate tiny grids.

Hook (above the fold):

100 large-print word searches for adults — medium difficulty, one puzzle per page, answers in the back.

Promise:

Quiet, focused puzzles without squinting: big type, clean grids, and a full answer key so you can check your work when you want to.

Proof:

• 100 original medium-difficulty word searches
• Large print designed for comfortable reading
• One puzzle per page — room to work
• Complete answer key at the end of the book

CTA (soft):

Open the free sample to check the grid size, then grab a copy for yourself or as a low-stress gift.

What this example does not include: star ratings, “#1 bestseller,” a website, a price, emoji, or “please review.” Those are the failure modes, not optional upgrades.

Your real book will swap the numbers and audience. The order of beats stays.

How long should a KDP book description be?

Use three different lengths in your head:

1. Above the fold — as short as it can be while still naming the book. Often one or two sentences; sometimes a bold line plus a blank line before the body.
2. KDP’s craft guidance — roughly a 150-word scannable block for the core idea (their “simple” guidance). Many strong listings run longer once you add structured sections.
3. Hard ceiling — 4,000 characters, and HTML tags count. A draft that is “under 4,000” in Google Docs can still overflow after you wrap headings and lists in Source view.

There is no official Amazon minimum. A description that is only a sentence wastes discovery and persuasion space you already paid for with the listing. A description that burns the whole budget on fluff is not better. Prefer specific and scannable over long.

How to use the KDP Description Generator

The KDP Description Generator is built for the publish step, not for generic AI prose:

1. Feed the facts first — title, genre or activity type, who it is for, what’s inside (counts, tone, series). Garbage in, vague blurb out.
2. Generate into valid HTML — the product goal is the twelve tags KDP documents, under the 4,000-character budget, without the prohibited promo patterns the listing rules flag.
3. Edit the hook by hand — keep generator output for structure and formatting; rewrite the first lines until they fit the above-the-fold test on your phone.
4. Paste into KDP Source view — confirm the character count in the official editor (it counts tags too).
5. Run a second pass with the free KDP Listing Checker if you changed the copy: length, HTML shape, and common restricted phrases.

For the whitelist, tag budgeting, and paste/strip traps, use the companion post: Which HTML Tags KDP Actually Supports.

Pre-publish checklist

Before you click Publish on the description:

• First two lines name what it is and who it is for without needing the rest
• Body follows hook → promise → proof → soft CTA
• No URLs, emails, phones, prices, stock claims, or “buy now” language
• No review quotes, star ratings, or “please leave a review”
• No emoji; no keyword-tag dump at the bottom
• No spoilers that give away the ending
• Claims match the interior (counts, level, format)
• HTML only uses supported tags; character count with tags is under 4,000
• You re-read it after a break (KDP’s “professional” bar is real: typos kill trust)

Descriptions are editable after publish via Edit details on the Bookshelf — unlike some title fields that lock early for print. Still treat the live detail page as customer-facing inventory: fix errors quickly, and do not use “I can edit later” as permission to ship a restricted draft.

FAQ

How do you write a book description for Amazon KDP?

Start with the reader’s itch, not a chapter-by-chapter summary. Write a short hook that earns Read more, a clear promise of what the book delivers, specific proof (contents, stakes, real credentials), and a soft close without promo language. Then format with only the HTML tags KDP supports and stay under 4,000 characters including tags. Use KDP’s Write a Book Description page as the rule source for limits and restrictions.

How long should an Amazon book description be?

KDP recommends simple, scannable language and sketches about 150 words for the core idea; the hard limit is 4,000 characters including HTML. Prioritize the first lines that appear before Read more, then add only as much body as stays specific. Empty length does not help ranking or conversion.

Can I put reviews or testimonials in my KDP description?

KDP’s help page lists reviews, quotes, or testimonials among information the description cannot accept, along with requests for customer reviews. Do not paste star ratings or “what readers are saying” blocks into the description field. Keep the blurb about the book itself.

Can I include my website or “buy now” in the description?

No. KDP restricts phone numbers, physical mail addresses, email addresses, and website URLs, plus availability, price, and alternative ordering information. “Buy now” / order-language is the same promotional family. The Amazon detail page already has the purchase controls.

Should I put keywords in the book description?

Use natural language a shopper would search for (genre, topic, activity type) inside real sentences. Do not dump a keyword list or “book tags” block into the description — KDP lists keywords or book tags phrases as restricted content there. Put discovery phrases that will not fit the blurb into the seven backend keyword fields instead.

What HTML can I use in a KDP book description?

KDP documents a short whitelist (breaks, paragraphs, bold/italic/underline, h4–h6, ordered/unordered lists). Tags count toward the 4,000-character limit. Full table, budgeting, and common paste failures: Which HTML Tags KDP Actually Supports.

Fiction vs nonfiction — does the structure change?

The beats stay the same. Fiction emphasizes conflict and tone without spoilers; nonfiction emphasizes problem, method, and authority; activity books emphasize counts, difficulty, and layout. Same skeleton, different proof.

Related free tools and guides

• KDP Description Generator — generate a description in valid KDP HTML under the character budget
• KDP Listing Checker — free pass over description length, HTML shape, and common restricted phrases
• Which HTML Tags KDP Actually Supports — the 12-tag whitelist and why tags count toward 4,000
• How to Choose KDP Categories — browse categories that match the promise in your blurb
• All free KDP tools

Disclaimer

Amazon, Kindle, KDP, and related marks are trademarks of Amazon.com, Inc. or its affiliates. SmartKDP is not affiliated with, endorsed by, or sponsored by Amazon. Always confirm description length, HTML, and content rules in your KDP account and current Amazon help documentation before you publish or update a live listing.