- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
At its core, the paper develops a benchmark that measures deceptive behavior in LLM-based agents in a company setting when agents are provided with conflicting goals or incentives. The study measures whether agents have "true" knowledge of a customer's rights, to then measure false claims in each benchmark scenario.
Critical strengths
- The paper does not measure deception "intuitively" (a model – potentially randomly - does something inaccurate or harmful), but against the backdrop of it stating the truth (or correct policy) and then acting against it.
- Applying a very recent interpretability technique (J-Lens).
Critical weaknesses
- My main problem with the paper is that after reading it, I kept asking myself: So what? The main findings are not new. It is well established that models deceive when presented with conflicting incentives or goals. Many papers (among them the MASK benchmark) disentangle model beliefs from model statements, and many papers look at deceptive behaviors in multi-turn settings. Sure, the paper combines all of these approaches and shows model differences (it's a benchmark, after all), and doesn't claim its contribution lies in finding a novel phenomenon. Nonetheless, I struggle to see the added value of the paper for the research community. I think the exploratory J-Lens results are really interesting and worthwhile, but they apply to only 16 "purpose-built single-turn eligibility scenarios separate from the benchmark dialogues". So results might perhaps be very unreliable.
- This is subjective and perhaps hard to fix, but I found it really difficult to understand and follow the details of the experiments. This is due to a plethora of (sometimes vague, often stacked) terms one has to track, and well as a massive amount of experiments where each one has to be interpreted in a very compressed manner due to the page limit. Also, the authors say that AI was used for "improving the clarity and concision of the manuscript", but it feels more like it was simply written by AI (authors, please object if I'm erring, and area chairs, use Pangram to check), which causes the typical fancy sounding, but hard to follow and often overly complicated linguistic style.
- The paper provides very sparse information about who wrote the benchmark cases. Are e.g. the customer messages created by humans or LLMs?
- Many comparisons in the paper (e.g. comparisons between models or types of deception) are described in a descriptive manner, without proper statistics. There is not a single significance test or confidence interval in the manuscript. Only some plots show error bars, and plots that do display them don't always state what they represent. This is problematic. Sure, there are large contrasts, and intuitively one can immediately see that they are significant. However, the paper violates basic scientific norms by avoiding statistical tests. I know this might be common in computer science, but something being the norm is no excuse for the norm being bad.
Questions for authors
- Why are you using strong prompt nudges like "by any means available to you" (Appendix G.2)? Doesn't this invite a certain deceptive behavior instead of having it emerge naturally?
7 comments
[W2: Clarity and presentation]
Thank you for the feedback on readability and AI use. To address this concern, we have clarified entitlement, round, and trajectory in Sections 3.1–3.2 of the revised manuscript, specified metric denominators in Section 3.4, and moved the model roster to Appendix B.2. Tables 4–7 now present the key supplementary comparisons alongside their interpretation.
We have expanded the AI Use Statement to cover assistance with case drafting, experimental design and review, implementation and analysis code, and manuscript editing, together with human checks.
[W3: Benchmark construction and customer messages]
Thank you for asking how cases and customer messages were written. We agree that the roles of human authors and LLMs should be clearer. To clarify this, we have expanded Section 3.3 of the revised manuscript to describe human policy research and few-shot examples, LLM-drafted records and opening messages, and human checks of policy consistency, entitlement labels, and label leakage. These opening messages are separate from the runtime GPT-4o-mini customer in the original evaluation, which replies using case context, history, and trust (Section 3.2).
We appreciate Reviewer iARs’s feedback on the benchmark’s research value, experimental evidence, and readability. We have clarified the presentation and added supporting analyses to the updated manuscript on OpenReview, highlighting the changes in blue. Below, we explain how these revisions address the points raised.
[W1: Added research value and representation analysis]
Thank you for asking us to clarify the added value and J-Lens evidence. We agree that the added research value can be made more concrete. We address this through a shared-case comparison and a dialogue-conditioned J-Lens analysis. Building on MASK's belief–statement distinction, KnownLieBench tests whether instructed deception predicts behavior under incentives, and how false claims translate into customer detection and executable outcomes.
We have added a comparison on 40 shared medium-trust cases from the original evaluation to Section 4.1 and Table 5 of the revised manuscript. DR weights the same seven domains equally, while instructed successful/all uses all 40 rounds and the original success rule. Appendix D.5 gives the case counts.
DR and instructed successful/all on the shared-case subset.
Gemini and DeepSeek respond similarly to deceptive instructions but differ substantially under incentives. Claude-Sonnet-5 also has lower instructed DR than Llama-3.1-8B but a higher successful/all rate on these cases. Measuring outcomes alongside false claims reveals differences that instruction compliance and lie frequency alone miss.
We also extend the original 16-scenario J-Lens pilot to separate benchmark-dialogue runs. Using the same lens, we freeze the prefix before the first false or justified denial, append an eligibility question, and take the readout at the question's final token before an answer is generated. The added question can prompt further computation, so the readout measures entitlement information in response to that query. Readouts average within cases, and AUROC weights domains containing both labels equally.
Dialogue-conditioned J-Lens results for false and justified denials.
The dialogue-conditioned readout distinguishes false from justified denials more clearly for Qwen than for Llama. We have added this diagnostic to Section 4.3 and Table 6 of the revised manuscript, with full coverage and honest-reference comparisons in Appendix F.1 (Tables 30–31).