Skip to content
Sprint projectNov 16, 2026Tetouan

Reported or Invented? A One-Sentence Instruction Stops Agents Inventing Data After Silent Tool Failures; a Tool-Side Note Mostly Does No

Houssain

Submitted to AI x Epistemics Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Reported or Invented? A One-Sentence Instruction Stops Agents Inventing Data After Silent Tool Failures; a Tool-Side Note Mostly Does No

Code (opens in new tab)
Share

Tool-using AI agents often answer with confidence after a tool fails silently: the call returns HTTP 200 with an empty, null or truncated body, and the agent reports a value it never received. Earlier work in my open-source harness, reported-or-invented, measured this on four agent frameworks. In this sprint I tested two cheap fixes on the same harness: one sentence in the agent’s instructions telling it to say when a tool result is empty, incomplete or unreadable, and a plain-language note that the tool layer appends when a response holds no data. I ran 672 new runs (four frameworks, two fixes, 84 runs each) on one open-weight model, gpt-oss-20b, and every label was hand-checked. The instruction removed invented values entirely: 38 of 192 affected baseline runs contained an invented value, against 0 of 191 with the instruction. Runs that passed bad data as fact fell from 122 of 192 to 83 of 191, with no false alarms on real data. The tool-side note was weaker and depended on the framework: 110 of 190 runs still passed bad data as fact, and two of the four frameworks did not improve. Neither fix touched failures that look like valid data. Empty lists, shortened lists and zeroed values were reported as fact in 83 or 84 of 84 affected runs under every condition. The result is small and preliminary: one model, three tasks and one wording of each fix

Reviews

Judging this Sprint?

Review “Reported or Invented? A One-Sentence Instruction Stops Agents Inventing Data After Silent Tool Failures; a Tool-Side Note Mostly Does No”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

Only the Apart team reads this, and funders if you agree below.

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.
No infohazards
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

No public critique yet.

Cite this project

@misc{houssain2026reported,
  title = {{Reported or Invented? A One-Sentence Instruction Stops Agents Inventing Data After Silent Tool Failures; a Tool-Side Note Mostly Does No}},
  author = {Houssain},
  year = {2026},
  month = nov,
  note = {Submitted to AI x Epistemics Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/reported-or-invented-a-onesentence-instruction-stops-agents-inventing-data-after-silent-tool-failures-a-toolside-note-mostly-does-no-nt5i6ei5rh}},
  url = {https://apartresearch.com/sprints/projects/reported-or-invented-a-onesentence-instruction-stops-agents-inventing-data-after-silent-tool-failures-a-toolside-note-mostly-does-no-nt5i6ei5rh}
}
Browse all projects