Describe the result, not just the activity
Start with the deliverable: a comparison, a draft, a checked set of records, or a concise recommendation. Add the audience and the facts the agent should treat as authoritative. If several outputs are needed, list them so you can review completeness instead of inferring it from a long conversation.
State constraints that change the answer, such as a deadline, allowed sources, naming rules, or a required format. A short example can clarify what a good result looks like. Avoid asking for unrelated work in the same request; a focused outcome is easier to evaluate and revise.
Set boundaries for consequential actions
Separate analysis from actions that affect other people or persistent data. Ask the agent to prepare a message or plan first when you want to approve it before it is sent or applied. Name the resources it may inspect and identify anything that must remain untouched.
When a task has several stages, ask for a checkpoint after the important decision rather than relying on a vague instruction to be careful. Review the proposed change against the original goal, then provide corrections in concrete terms. This gives the agent useful direction while keeping your judgment in the loop.