The last but equally crucial element of prompt engineering is setting expectations. This is where you define the form of the response. Even if the goal, context, and source are perfect, unclear expectations will dilute the output.
Think about asking someone for a recommendation. Do you want a single suggestion? A ranked list? A one-liner? A paragraph? A pros-and-cons comparison? Without telling them, they’ll default to whatever feels natural to them not necessarily to you.
AI works the same way. Left to its own devices, it may output in ways that surprise you. That’s ambiguity. Unless you are doing some intentional exploration, otherwise it’s always good to specify clearly what you want from AI.
Instead of just saying, “List our top 5 products,” say, “List our top 5 products in a table with columns for name, customer segment, average rating, and unique selling point. Keep the tone casual but informative.”
Or if you’re asking for analysis, instead of “Summarize this,” say, “Summarize this research article into three paragraphs: one on findings, one on implications, and one on next steps. Make it readable for a non-expert audience.”
Setting expectations means defining:
- The format (table, list, paragraph, portrait, landscape)
- The tone (formal, friendly, academic, humorous)
- The length or scope (word count, number of points, time constraints)
- The style — for visuals (e.g that famous Ghibli style)
You don’t need to micromanage every detail but think like a director giving stage notes to a talented actor. The more clearly you describe the performance you want, the better the show will be.