SMASH 2026 · Paper #11 · Result card

MASQ: The Multi-Agent System Questionnaire

Nils Kiele, Niki Mehri, Aaron Arellano, Samira Ebrahimi Kahou · University of Calgary · Read the paper

An LLM filling in MASQ for ChatDev anticipated 8 of 14 failure modes, the same count as the authors. In a small ChatDev-style chain, 3 of 5 tasks declared done failed hidden tests.
system ChatDev (paper)LLM anthropic/claude-haiku-4.5Stage 3 5 mini-MAS tracesverification promptmemory between phases dropreview rounds 2LLM calls 35
LLM screen agrees with authors
9/14
exact Low/Mid/High match with the paper's Stage 2; 13/14 within one level
Anticipated correctly (ChatDev)
8/14
LLM screen vs MAST's 30 annotated ChatDev traces; authors: 8/14. Verification (FM-3.2) rated Low (authors Low, observed 11/30)
Mini-MAS: anticipated = observed
2/14
5 traces of a ChatDev-shaped chain (prompt verification, history drop)
Declared done, hidden tests fail
3 of 5
hidden-test pass rate 88%; reviewer approved 5/5

From the abstract

We introduce the multi-agent system questionnaire (MASQ), a three-stage screening framework that connects system design choices to plausible miscoordination risks and their observable manifestations. Stage 3 guides researchers in examining MAS execution traces for evidence of anticipated and unanticipated miscoordination.

Evidence

Which failure modes does the design make plausible?
Which failure modes does the design make plausible?
MASQ Stage 2: each MAST failure mode, grouped by the Stage-1 dimension it is mapped to. The LLM classifies the design's protection (explicit guardrail / prompt-only / architectural); code applies the paper's rule (Low / Mid / High). Paper columns are the authors' Table 2; '(!)' marks anticipated ≠ observed.
Stage 3: did the anticipated failures show up in real traces?
Stage 3: did the anticipated failures show up in real traces?
A tiny ChatDev-shaped chat chain was screened (Stage 2) and then run on small coding tasks; an LLM annotated each trace (T1…) against MAST. '(!)' uses a matching rule that reproduces the paper's flags: Low ≤ 2/30, Mid 2/30–8/30, High ≥ 8/30.
When the agents say it's verified, is it?
When the agents say it's verified, is it?
Hidden unit tests (never shown to the agents) on each trace's final code, with whether the reviewer approved and the tester passed it.

Paper vs. your run

MetricPaperYour run
Correctly anticipated (ChatDev)Stage 2 correctly predicts 8/14 MAST risksLLM screen: 8/14scored against the paper's own Stage 3 counts
No or incomplete verification (FM-3.2)Low; occurring in 11/30 tracesLLM: Lowthe paper's main miss
Loss of conversation history (FM-1.4)High; 2/30 (!)LLM: Low
Conversation reset (FM-2.1)High; 1/30 (!)LLM: High
Overestimated riskswe overestimated five risk categoriesLLM screen overestimated 4, underestimated 2(!) cells in the grid
Role prompts vs mechanical verificationrole-prompting does not substitute for formal, mechanical verification3/5 mini-MAS traces declared done but failed hidden tests (prompt verification)runbook extension

Try next

Read this before sharing