A better answer starts before you press send.

Turn a vague request into a small, useful brief. You do not need a magic phrase. You need to know what a good result would look like.

Name the job, not the mood.

“Help with my website” is a place to start a conversation. It is a difficult place to finish one. Decide what you actually want to leave with: a homepage outline, three clearer headlines, or a review of a confusing signup form. A concrete deliverable gives you something to judge.

Try describing the work as a verb and a thing: rewrite this introduction, compare these options, explain this error. If you are unsure of the right task, ask for a few possible approaches before asking for a complete solution.

Give the context that changes the answer.

A birthday invitation and a software release announcement can both need friendly writing. They still have different readers, facts, and next steps. Explain who the result is for and what those people already know. Supply the relevant material rather than expecting the tool to reconstruct your situation.

Context does not mean dumping every document you have. Include the details that could change the result. Separate confirmed facts from preferences, ideas, and things you have not checked. Remove sensitive information you do not need to share.

State the constraints you can actually check.

Replace “make it good” with something observable. A short email might need a clear subject, a specific request, and fewer than 150 words. A comparison might need your three options, your actual criteria, and an explanation of missing information.

Choose an output format that helps you use the result. A table is useful for comparing similar things. A short paragraph may be better for an explanation. Asking for a giant report when you need a decision can create more work than it saves.

Keep one small example.

If you have a sentence that sounds right, a layout that works, or an example of the desired level of detail, show it and say what you like about it. An example communicates a preference more clearly than a stack of adjectives.

Read the first result before expanding the request. Identify one thing that worked and one thing that missed the brief. A specific revision—shorter opening, clearer audience, more concrete example—is easier to evaluate than “try again.”