How do you write a prompt that gets a useful answer?

Why the wording matters

A prompt is simply the message you type into an AI tool. Because the tool builds its reply from the words you give it, the quality of your request shapes the quality of the answer. Google's prompt design guide for its Gemini models starts with the same basic advice: give clear and specific instructions [1].

You do not need special tricks. You need the same things a capable new employee would need from you on their first day.

The five parts of a useful prompt

1. Role. Tell the tool what kind of helper to be. "You are a friendly front-desk assistant for a landscaping company" sets the voice and the point of view. Google's prompt design guide recommends placing role definitions, which it also calls a persona, at the very beginning of the prompt [1].

2. Facts. Give it the details it cannot know: your prices, hours, service area, the customer's question, the notes from your meeting. Google's guide recommends including the information the model needs to solve the problem, instead of assuming it already has everything it needs [1]. If you leave out a fact, the tool may fill the gap with something that sounds right and is not.

3. Goal. Say what the answer is for. "Write a reply that answers the question and invites them to book a visit" is far clearer than "Respond to this."

4. Format. Describe the shape you want: three bullet points, a two-sentence text message, a table with two columns, under 100 words. Google's guide notes you can give instructions that specify the format of the response, along with any limits it should respect [1].

5. Example. If you have a message you like, paste it in and say "match this tone." Google's guide calls this including examples, or "few-shot" prompting, so the tool can pick up the pattern you want, and it recommends always including examples [1].

You will not need all five every time. For a quick rewrite, a goal and a format may be enough. For anything a customer will see, use all five.

Iterate instead of starting over

The first reply is rarely the final one. Google's guide says plainly that prompt design can take a few rounds before you get the response you want [1]. That is normal.

Good follow-up requests are short and specific:

• "Shorter. Two sentences."
• "Less formal. Sound like a neighbor, not a lawyer."
• "Keep the second paragraph, rewrite the opening."
• "You used a price I did not give you. Remove it."

If a task has many parts, split it up. Google's guide suggests breaking a complex job into smaller prompts, one instruction each, instead of packing everything into one request [1]. Ask for an outline first, then each section.

Save the prompts that work

When a prompt gives you a great result, save it in a document with a short name, like "Review reply" or "Listing description." Next time, you paste it in and only change the facts. Over a few weeks you build a small library that saves real time and keeps your messages consistent.

Common mistakes

One-line requests. "Write a post about our sale" gives the tool almost nothing. Add the dates, the offer, the audience and the tone.

Leaving out key facts. If you do not give a price, the tool may invent one. Give it the facts or tell it to leave a blank.

Asking for everything at once. A request for a full marketing plan, five posts and an email in one message tends to produce thin results. Ask in steps.

Accepting the first draft. A quick follow-up request usually fixes what is off. Asking for changes is part of the process, not a sign it failed.

Worked example

A real estate agent wants a short listing description.

Weak prompt: "Write a listing for a 3-bed house."

Stronger prompt:

You are writing for a real estate agent's listing page. Facts: 3 bedrooms, 2 bathrooms, 1,850 square feet, built in 1998, new roof in 2023, two-car garage, fenced backyard, kitchen updated with quartz counters. Goal: a description that helps buyers picture the home and invites them to schedule a showing. Format: about 100 words, one paragraph, then one line with the call to action. Rules: only use the facts above. Do not describe the neighborhood, the street or the schools, and do not use words like "quiet," "safe" or "perfect."

The second prompt gives the role, the facts, the goal, the format and clear limits. The agent reads the result, checks every detail against the listing sheet, and asks for one change: "Mention the garage earlier." Two rounds, and the draft is ready for her final review.

Checklist

• I said what role the tool should take.
• I gave it the facts it needs and told it not to add others.
• I stated the goal of the answer.
• I described the format and length.
• I included an example when I had one.
• I asked for at least one round of changes before using the result.

Try it

Pick a message you write often, such as a reply to a new inquiry. Write a prompt using all five parts: role, facts, goal, format, example. Run it, then ask for one change. When you like the result, save the prompt in a document called "My prompts."

Tips

• Write prompts the way you would brief a capable new hire.
• Tell the tool to use only the facts you gave it.
• Ask for two or three options when you are not sure what you want.
• Keep a document of prompts that work and reuse them.

Sources

1. Google, "Prompt design strategies," Gemini API documentation, https://ai.google.dev/gemini-api/docs/prompting-strategies