A polished research brief can feel persuasive before it is useful. The first design question is whether a reader can trace each important claim back to the material that supports it.
Separate discovery from support
Search results help locate material. They are not a substitute for reading it. Ask the agent to collect the original page, its date, the relevant passage, and the claim it supports. A source table is often more useful than another paragraph of confident synthesis.
Keep disagreement visible
When sources disagree, preserve both positions and explain the difference in scope. One source might describe a product announcement while another describes an individual experience. They should not be collapsed into a universal result.
Use a claim ledger
A simple ledger can contain four columns: claim, source, limitation, and review status. This gives a human a compact way to inspect the work. Mark claims as supported, uncertain, or unsupported; do not turn the number of links into a truth score.
Review what matters most
Start with claims that drive the recommendation. Open the original sources and check whether the wording supports the conclusion. Remove claims that cannot be traced. The result may be shorter, but the reader will know what it rests on.
For the illustrative research-brief use case in this directory, the expected deliverable is a brief plus a source ledger. No claim of real-world performance is implied.