Describe the result and the working context
Start with the finished outcome rather than a list of vague activities. For example, name the document to update, the sections that matter, and whether you expect a summary, a code change, or a customer-facing article.
Point the agent to authoritative sources and explain domain terms that may be ambiguous. If several files or environments look similar, specify the correct one and note any dependencies the agent should inspect before making a change.
Set boundaries and review criteria
Call out constraints such as supported languages, URL format, compatibility requirements, or actions that need approval. Mention concrete acceptance criteria so the final report can show what was checked and what remains uncertain.
Avoid including secrets or unrelated personal data in a task brief. After the agent finishes, compare the result with the requested outcome, inspect consequential changes, and correct the brief if the work revealed a missing requirement.