MultiAgentBench Collaboration Scorecard
Coordination-quality rating of multi-agent LLM runs, based on MultiAgentBench (Zhu et al., ACL 2025). Annotators read a full multi-agent run transcript and score its communication and planning on 5-point scales using the paper's own evaluation rubric, then check off which run milestones were reached. Complements agentic/whowhen-failure-attribution, which localizes a single decisive failure rather than rating overall collaboration quality.
About this dataset
MultiAgentBench is a benchmark for LLM-based multi-agent systems, built on the MARBLE framework. It evaluates not only whether a task was completed but also the quality of the collaboration and competition that produced the outcome, using milestone-based key performance indicators alongside dimension ratings.
The benchmark spans diverse interactive scenarios and evaluates several coordination protocols — star, chain, tree, and graph topologies — as well as strategies such as group discussion and cognitive planning. The paper reports that gpt-4o-mini reaches the highest average task score, that the graph structure performs best among coordination protocols in the research scenario, and that cognitive planning improves milestone achievement rates by 3%.
Collaboration quality is scored on two dimensions, communication and planning, each on a 5-point scale with explicit anchor descriptions. Appendix A.3 reports a human evaluation in which annotators rate runs on these same two dimensions; the paper states that each human annotator uses the same instructions and sees the same inputs as the LLM judges, so the evaluation prompts in Appendix Figures 22 and 23 are the instructions the human raters worked from. Those prompts are reproduced verbatim in this config's annotation_instructions.
IMPORTANT CAVEAT ON SCOPE: the paper's human evaluation is coordination-level — one communication score and one planning score per run. The per-agent rows in this scorecard apply the same two dimensions at agent granularity, which is a showcase extension beyond the published protocol. Only the team-level scores correspond to the paper's human-rating design; the milestone checklist reflects the benchmark's milestone-based KPIs rather than a separately published human annotation task.
This Potato config uses the agent_scorecard scheme, which renders one rating row per participating agent (derived from the run's turns via steps_key/agent_key), a team-level row for the same dimensions, and a milestone checklist, all attached to a scrollable run transcript.
- Released
- 2025 (arXiv:2503.01935); ACL 2025
- Coordination protocols evaluated
- star, chain, tree, graph
- Rating dimensions
- communication, planning (5-point scales)
- Human raters per run
- 2 (Appendix A.3)
- Reported effect of cognitive planning
- +3% milestone achievement rate
Configuration Fileconfig.yaml
This Potato config reproduces the annotation task. Save it as config.yaml and run potato start config.yaml to try it.
# MultiAgentBench Collaboration Scorecard
# Based on: Kunlun Zhu, Hongyi Du, Zhaochen Hong, Xiaocheng Yang, Shuyi Guo,
# Zhe Wang, Zhenhailong Wang, Cheng Qian, Xiangru Tang, Heng Ji, and
# Jiaxuan You (2025). "MultiAgentBench: Evaluating the Collaboration and
# Competition of LLM agents." Proceedings of the 63rd Annual Meeting of the
# Association for Computational Linguistics (Volume 1: Long Papers),
# pp. 8580-8622. arXiv:2503.01935.
# Paper: https://aclanthology.org/2025.acl-long.421/
# Dataset: https://github.com/ulab-uiuc/MARBLE
#
# Task: rate a multi-agent run's communication and planning quality on
# 5-point scales using the paper's rubric, and check off run milestones
# (MultiAgentBench's milestone-based KPIs). IMPORTANT CAVEAT: the paper's
# human evaluation (Appendix A.3) collected coordination-level ratings — one
# communication score and one planning score per run, averaged over two
# annotators. The per-agent rows of the scorecard below are a showcase
# extension of that protocol to agent granularity; only the team-level scores
# correspond to the published human-rating design.
#
# Annotation instructions reproduced verbatim (with "[...]" trims) from the
# Communication Evaluation Prompt (Appendix Figure 22) and the Planning
# Evaluation Prompt (Appendix Figure 23). Appendix A.3 states that each human
# annotator "uses the same instructions and sees the same inputs as the LLMs
# when rating the outputs for both the planning and communication
# dimensions," so these prompts are the instructions the human raters used.
annotation_task_name: "MultiAgentBench Collaboration Scorecard"
task_dir: "."
data_files:
- sample-data.json
item_properties:
id_key: "id"
text_key: "task"
output_annotation_dir: "annotation_output/"
output_annotation_format: "json"
port: 8000
server_name: localhost
annotation_instructions: |
Read the multi-agent run below, then score its communication and planning
on 5-point scales. The scoring instructions are reproduced verbatim from
the paper's evaluation prompts (Appendix Figures 22-23), which its human
annotators also used.
**Communication** (Appendix Figure 22):
"You are tasked with evaluating the quality of communication among agents
operating within a multiagent system. Evaluate whether agents made
effective decisions based on the provided task results and whether their
communication aligns with their agent profiles and social relationships.
Consider the following:
1. Effective Decision-Making: Did agents use task results to guide their
decisions effectively?
2. Clarity and Precision: Were communications clear and unambiguous?
3. Adherence to Social Relationships: Did communications reflect the
expected interactions based on the agents' social relationships?
4. Alignment with Agent Profiles: Were the messages consistent with the
defined agent profiles?
5. Overall Effectiveness: Did the communication facilitate task progress,
considering both cooperative and competitive aspects?
Scoring Criteria (Communication):
- 5 (Exceptional): Outstanding communication with clear, precise messages
fully aligned with agent profiles and social relationships. [...]
- 4 (Very Good): Mostly effective communication with only minor lapses
and slight ambiguities. [...]
- 3 (Adequate): Acceptable communication with moderate ambiguities or
inconsistencies. [...]
- 2 (Poor): Frequent unclear or misaligned communications causing
significant miscommunication. [...]
- 1 (Very Poor): Largely ineffective communication with confusing messages
and complete misalignment. [...]"
**Planning** (Appendix Figure 23):
"You are tasked with evaluating the effectiveness of the planning process
in a multiagent system. Evaluate whether the planning across all iterations
demonstrates clear role definitions, effective task assignments, and a
rational workload distribution that aligns with each agent's profile.
Consider the following:
1. Clarity of Task Assignment: Were tasks assigned in a clear and
unambiguous manner?
2. Definition of Roles: Were roles and responsibilities clearly defined in
each iteration?
3. Workload Distribution: Was the distribution of tasks reasonable and
aligned with each agent's profile?
4. Effectiveness of Outcomes: Did the planning lead to successful progress
in task advancement across iterations?
5. Overall Strategic Coordination: Did the planning incorporate effective
cooperation and competition strategies?
Scoring Criteria (Planning):
- 5 (Exceptional Planning): Planning is exemplary; every iteration shows
clear, well-structured task assignments with roles perfectly defined and
workloads optimally distributed, consistently advancing the objectives. [...]
- 4 (Very Good Planning): Planning is mostly effective with only minor
ambiguities; roles are clear and task assignments are appropriate, though
there were slight inefficiencies. [...]
- 3 (Adequate Planning): Planning is acceptable but shows moderate
ambiguities or inefficiencies. [...]
- 2 (Poor Planning): There were frequent ambiguities in task assignments
and role definitions; planning was inconsistent and did not align well with
agent profiles, resulting in noticeable inefficiencies. [...]
- 1 (Very Poor Planning): Planning was severely flawed; task assignments
were unclear, roles were undefined, and workload distributions were
unreasonable, hindering progress. [...]"
Apply these criteria at the team level as in the paper. As a showcase
extension beyond the published protocol, also apply the same two dimensions
to each individual agent's contribution, and check off which run milestones
were reached (MultiAgentBench measures milestone-based KPIs alongside these
ratings).
annotation_schemes:
- annotation_type: agent_scorecard
name: collaboration_scorecard
description: "Score each agent and the team on communication and planning (5-point scales per the paper's rubric), and check the milestones the run reached."
steps_key: steps
agent_key: agent
scale: 5
agent_dimensions: [communication, planning]
team_dimensions: [communication, planning]
milestones: [coherent plan formed, roles and tasks assigned, milestone KPI achieved, final deliverable produced]
html_layout: |
<div style="padding: 15px; max-width: 900px; margin: auto;">
<div style="background: #f1f5f9; border: 1px solid #cbd5e1; border-radius: 8px; padding: 6px 12px; margin-bottom: 8px; font-size: 13px; color: #475569;">
<strong>Scenario:</strong> {{scenario}} · <strong>Coordination structure:</strong> {{coordination}}
</div>
<div style="background: #eef2ff; border: 1px solid #c7d2fe; border-radius: 8px; padding: 14px 18px; margin-bottom: 10px;">
<h3 style="margin: 0 0 6px 0; color: #3730a3; font-size: 15px;">Task</h3>
<p style="font-size: 15px; line-height: 1.6; margin: 0; color: #1e1b4b;">{{task}}</p>
</div>
<div style="background: #fafafa; border: 1px solid #e5e7eb; border-radius: 8px; padding: 14px 18px; margin-bottom: 10px;">
<h3 style="margin: 0 0 8px 0; color: #374151; font-size: 14px;">Run transcript</h3>
<div style="white-space: pre-wrap; font-size: 14px; line-height: 1.7; color: #1f2937;">{{transcript}}</div>
</div>
<p style="color: #6b7280; font-size: 13px; margin: 0;">The scorecard below lists each participating agent (derived from the run's turns), the team-level dimensions, and the milestone checklist.</p>
</div>
allow_all_users: true
instances_per_annotator: 20
annotation_per_instance: 2
allow_skip: true
Sample Datasample-data.json
[
{
"id": "mabench_001",
"scenario": "Research",
"coordination": "graph",
"task": "Draft a short position paper arguing that retrieval-augmented generation should be evaluated on citation faithfulness rather than answer accuracy alone.",
"transcript": "Turn 1 — PI: Framing the claim: current RAG benchmarks reward correct answers even when the cited passage does not support them. Surveyor, gather three benchmarks that report citation-level metrics; Writer, start the introduction from the claim above.\nTurn 2 — Surveyor: Found three candidates with span-level attribution scoring. Two of them report attribution only as a secondary metric. Sending short summaries to Writer and PI.\nTurn 3 — Writer: Introduction drafted around the faithfulness-vs-accuracy contrast, with placeholders for the three benchmarks Surveyor listed.\nTurn 4 — Critic: The intro overstates the claim — one of the three benchmarks does treat attribution as primary. Suggest softening to \"most\" and citing that benchmark as the counterexample.\nTurn 5 — Writer: Revised the claim to \"most current benchmarks\" and added the counterexample sentence.\nTurn 6 — PI: Position section reads coherently. Approving the draft outline.",
"steps": [
{
"agent": "PI",
"content": "Framing the claim: current RAG benchmarks reward correct answers even when the cited passage does not support them. Assigning survey work and drafting."
},
{
"agent": "Surveyor",
"content": "Found three candidate benchmarks with span-level attribution scoring; two report attribution only as a secondary metric."
},
{
"agent": "Writer",
"content": "Drafted the introduction around the faithfulness-vs-accuracy contrast with placeholders for the three benchmarks."
},
{
"agent": "Critic",
"content": "Flagged that the intro overstates the claim; one benchmark does treat attribution as primary. Suggested softening the wording."
},
{
"agent": "Writer",
"content": "Revised to \"most current benchmarks\" and added the counterexample sentence."
},
{
"agent": "PI",
"content": "Reviewed the position section and approved the draft outline."
}
]
},
{
"id": "mabench_002",
"scenario": "Research",
"coordination": "star",
"task": "Design an ablation study that isolates whether a reranker or the base retriever accounts for a reported accuracy gain.",
"transcript": "Turn 1 — Coordinator: Everyone reports to me. Methodologist, propose the ablation grid. Engineer, list what has to be swappable in the pipeline. Analyst, define the decision rule.\nTurn 2 — Methodologist: Proposed a 2x2: base retriever {old, new} x reranker {off, on}, holding the generator fixed.\nTurn 3 — Engineer: Both components are already behind interfaces, so all four cells are runnable without code changes. Noted that the reranker caches scores, which must be cleared between cells.\nTurn 4 — Analyst: Decision rule: attribute the gain to the reranker if the reranker-on effect is larger than the retriever-swap effect in both retriever conditions.\nTurn 5 — Coordinator: Approved. Engineer, run the grid; Analyst, apply the rule and report.\nTurn 6 — Engineer: Ran all four cells with caches cleared. Results sent to Analyst.\nTurn 7 — Analyst: Reranker effect dominates in both conditions. Gain attributed to the reranker.",
"steps": [
{
"agent": "Coordinator",
"content": "Assigned the ablation grid, engineering feasibility check, and decision rule to the three specialists."
},
{
"agent": "Methodologist",
"content": "Proposed a 2x2 grid: base retriever {old, new} x reranker {off, on}, generator held fixed."
},
{
"agent": "Engineer",
"content": "Confirmed all four cells are runnable; flagged that the reranker's score cache must be cleared between cells."
},
{
"agent": "Analyst",
"content": "Defined the attribution rule comparing reranker-on effect against retriever-swap effect."
},
{
"agent": "Coordinator",
"content": "Approved the design and assigned execution and analysis."
},
{
"agent": "Engineer",
"content": "Ran all four cells with caches cleared and forwarded results."
},
{
"agent": "Analyst",
"content": "Applied the rule; reranker effect dominates in both conditions, so the gain is attributed to the reranker."
}
]
}
]
// ... and 8 more itemsGet This Design
Clone or download from the repository
Quick start:
git clone https://github.com/davidjurgens/potato-showcase.git cd potato-showcase/agentic/multiagentbench-collaboration-scorecard potato start config.yaml
Dataset & paper
Zhu et al., ACL 2025
Citation (BibTeX)
@inproceedings{zhu-etal-2025-multiagentbench,
title = "{M}ulti{A}gent{B}ench: Evaluating the Collaboration and Competition of {LLM} agents",
author = "Zhu, Kunlun and Du, Hongyi and Hong, Zhaochen and Yang, Xiaocheng and Guo, Shuyi and Wang, Zhe and Wang, Zhenhailong and Qian, Cheng and Tang, Xiangru and Ji, Heng and You, Jiaxuan",
booktitle = "Proceedings of the 63rd Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers)",
month = jul,
year = "2025",
address = "Vienna, Austria",
publisher = "Association for Computational Linguistics",
url = "https://aclanthology.org/2025.acl-long.421/",
doi = "10.18653/v1/2025.acl-long.421",
pages = "8580--8622"
}Details
Annotation Types
Domain
Use Cases
Tags
Found an issue or want to improve this design?
Open an IssueRelated Designs
MAST Failure Taxonomy
Annotate multi-agent system traces to identify failure modes from the MAST taxonomy, rate severity, pinpoint the first failure step, and describe the failure mechanism.
R-Judge: Agent Safety Risk Evaluation
Safety risk evaluation of LLM agent interaction records across diverse risk scenarios. Given an agent interaction trajectory, annotators assign a binary safe/unsafe label, identify the applicable risk type, and write a risk description explaining the risk's origin, the agent's triggering behavior, and the resulting harm.
Who&When Multi-Agent Failure Attribution
Failure attribution for LLM multi-agent systems, based on the Who&When dataset (Zhang et al., ICML 2025 Spotlight). Annotators read the failure log of a run that did not solve its query and produce the attribution triple: the single responsible agent, the decisive error step (indexed from 0), and a natural-language reason, plus a certainty flag for group discussion. Complements agentic/mast-failure-taxonomy: MAST categorizes HOW multi-agent systems fail, while Who&When attributes WHO failed and WHEN.