How Many Instructions
Can LLMs Follow at Once?

Daniel Jaroslawicz, Brendan Whiting, Parth Shah, Karime Maamari

Distyl AI  ·  {daniel, brendan, parth, karime}@distyl.ai

NeurIPS 2025 LLM Evaluation Workshop Poster

INFONET Journal Club  ·  May 29, 2026
Presenter: Donghyeon Kim

Why I Chose This Paper

Personal Context

While developing Shortcut, I repeatedly encountered a problem:

When multiple unrelated instructions are given at once, the LLM drops some or degrades in quality.
e.g., "summarize my emails" + "draft a reply" + "add to calendar" → first task done well, the rest ignored.

I'm exploring MAS / Dynamically Self-Structured MAS to address this. But before any of that — before proof of concept, before experiments — I needed a way to measure the problem first.

The IFScale benchmark solves this by quantifying how instruction-following degrades as the number of instructions increases.

Motivation

Recent models push context windows past 1M tokens: DeepSeek V4 Pro, Claude Opus 4.7, Gemini 2.5 Pro, and more.

The common assumption: if it fits in the context window, the LLM will handle it.

Researchers have uncovered common failure patterns in LLMs — primacy effects, silent instruction dropping, quality degradation under multiple constraints.

At the time of publication, none of these had been systematically measured as instruction density scales.

BenchmarkWhat They TestThe GapIFScale's Answer
FollowBenchMulti-constraint tasks
e.g., "Write 300 words, include a table, end politely"
Only 5–10 per promptTests 10 to 500
ComplexBenchMulti-step compositions
e.g., "Summarize, then translate, then format as JSON"
Complex but few instructionsSystematically varies count
IFEvalVerifiable constraints
e.g., "Use 4 paragraphs, start with Dear, no commas"
Fixed count, never variedVaries density in steps of 10
InfoBenchDiverse instruction types
e.g., "Respond in French, use bullet points, avoid very"
Count not a variableMakes count the independent variable
DIM-BenchDistractor resilience
e.g., "Write a summary (ignore: list primes under 100)"
Only tests irrelevant instructionsMeasures relevant instruction-following across densities

Context windows have grown from thousands to a million tokens. But as the table shows, no existing benchmark tests how instruction-following degrades when instruction count itself becomes the variable — even though omission errors and primacy effects are already known problems.

M — Methods

Task & Evaluation

IFScale — a benchmark measuring instruction-following degradation as instruction count scales from 10 to 500. 20 models, 7 providers, 50 density levels, 5 seeds each.

The Task

Write a professional business report. Include every keyword from the instruction list. Each instruction is a single constraint:

"Include the exact word accountability"
"Include the exact word strategy"
"Include the exact word compliance"

… × N instructions. Only the count changes — 10, 20, 30, …, 500. The task stays the same.

Why this works: simple enough to grade with regex — no ambiguity. The underlying job never changes, so instruction count is the only variable.

Exact match
→ counted as satisfied.
e.g., "accountability" appears
Partial (≥80% prefix)
→ modification error (not satisfied).
e.g., "accountable" instead
Not found
→ omission error (not satisfied).
e.g., never appears
Accuracy = keywords satisfied ÷ N

Each density level runs 5 times with different random seeds. The graph plots the average with ±1 standard deviation. o4-mini checks coherence (1–10); outputs that are only keyword lists, too short, or score below 6 are retried.

M — Methods

Vocabulary Construction Pipeline

How 500 curated business terms were created from SEC 10-K filings (business reports)

STEP 1 Extract o4-mini extracts top 500 candidate terms per SEC 10-K filing
STEP 2 Deduplicate Fuzz-match across all filings to remove duplicates
STEP 3 Validate Look-back check: term must appear as a whole word in the raw 10-K corpus
STEP 4 Filter & Normalize Zipf frequency ≥ 1.0 + WordNet lemmatization to collapse morphological variants
STEP 5 Semantic Dedup text-embedding-3-small → cosine similarity → prune near-duplicate meanings
STEP 6 Rank & Select Perplexity via gpt-4.1-nano → top 500 by generation difficulty
Result: 500 high-precision, business-relevant, non-redundant terms with exactly one form each. Full vocabulary in Appendix E of the paper.
M — Methods

Experiment Setup

Models Evaluated (20)

ProviderModels
OpenAIo3r, o4-minir, gpt-4o, gpt-4.1, gpt-4.1-mini, gpt-4.1-nano
Anthropicclaude-opus-4, claude-sonnet-4, claude-3.7-sonnet, claude-3.5-haiku (+ reasoning variants)
Googlegemini-2.5-pror, gemini-2.5-flash
xAIgrok-3-beta, grok-3-mini
Metallama-4-maverick, llama-4-scout
DeepSeekdeepseek-r1r
Alibabaqwen3

r = reasoning mode

Protocol — Design Rationale

Density levels10, 20, …, 500 (50 levels, step of 10)Smooth degradation curve, granularity
5 seeds per levelIndependent random seedsStatistical stability, variance measurement
Stratified samplingConsistent difficulty across levelsFair comparison, no difficulty drift
APIOpenRouter, default generation paramsNatural generation, no tuning bias
Reasoning effort"high" where applicableMaximize reasoning model capability

Six Metrics

Accuracy% of required keywords the model successfully includes
Std DevHow much accuracy varies across 5 runs — measures consistency
Omission RateHow often keywords are completely missing vs. approximated
Primacy RatioErrors in last ⅓ ÷ errors in first ⅓ — measures position bias
LatencyTime from prompt to completed output, in seconds
Coherenceo4-mini rates report quality on a 1–10 rubric
R — Results

Overall Performance

Model performance across instruction densities
Figure 2: Each line = one model. X-axis = number of instructions (10→500). Y-axis = accuracy (%). Colder colors = lower latency, warmer = higher. Shaded band = ±1 standard deviation across 5 runs. Models ranked by accuracy at 500 instructions.
How to read this: At low densities (left), most models score near 100%. As density increases (right), lines diverge — revealing each model's capacity limit. The shaded band shows how consistent the model is across repeated runs.
Top 3 at 500: gemini-2.5-pro 67.3% · o3 62.8% · grok-3 61.9%
Surprises: claude-3.7-sonnet beats newer claude-opus-4 · deepseek-r1 underperforms its reasoning label · gpt-4o decays like a much smaller model
R — Results

Three Degradation Patterns

Three degradation patterns
Figure 1: Three panels — one per degradation pattern. X-axis = instruction count, Y-axis = accuracy. Note how the shape of the drop differs fundamentally between patterns.
Threshold Decay
Holds near-perfect until a critical point, then drops steeply with rising variance. What this means: the model has a capacity cliff — it's reliable right up until it isn't.
o3, gemini-2.5-pro
Linear Decay
Steady, predictable decline across all densities. What this means: you can estimate accuracy for any instruction count — no sudden surprises.
gpt-4.1, claude-sonnet-4
Exponential Decay
Rapid early drop, then flatlines at ~7–15%. What this means: overwhelmed by even a few dozen instructions — don't use beyond 50.
gpt-4o, llama-4-scout
R — Results

Primacy Effects

Primacy effect ratios
Figure 3: Each line = one model. Y-axis = primacy ratio (errors in last ⅓ ÷ first ⅓). Ratio > 1.0 (dashed line) = later instructions are violated more often. Curves smoothed with rolling window of 3.

How to Read This

$$\text{Primacy Ratio} = \dfrac{\text{errors(last }\frac{1}{3})}{\text{errors(first }\frac{1}{3})}\quad \begin{cases} > 1.0 & \text{later violated more} \\ = 1.0 & \text{no bias} \\ < 1.0 & \text{earlier violated more} \end{cases}$$

  • Near 1.0 at low density: healthy — no position bias
  • Rising above 1.0: bias toward early instructions grows
  • Falling to 1.0 at high density: uniform collapse, not recovery

The Universal Pattern

  1. Low (10–50): ratios near 1.0
  2. Mid (150–200): ratios peak — selective attention under strain
  3. Extreme (300+): converge to 1.0–1.5 — uniform failure

Put important instructions first — but at extreme densities, ordering stops helping.

R — Results

How Models Fail — Omission Takes Over

Two Ways to Fail

Omission — keyword completely absent
"Include accountability" → (not found)
Modification — morphological variant appears
"Include accountability" → "...held accountable..."

The Shift

At low densities, errors are balanced. As density increases, omission takes over.

Omission Rate at 500 Instructions

ModelO:M at 500What This Means
llama-4-scout34.9drops keywords, almost never approximates
claude-3.5-haiku31.7
llama-4-maverick20+
claude-opus-4 (r)4.1still attempts approximations
gemini-2.5-pro↓ as density ↑ratio decreases — tries harder under load
When overwhelmed, models stop trying — they drop instructions entirely rather than attempt approximations.
R — Results

Efficiency — Accuracy vs. Latency

Latency Explosion (Reasoning Models)

Model10 inst.250 inst.
o4-mini r12.4s436.2s
o3 r26.3s219.6s
claude-3.5-haiku9.3s10.5s
gpt-4o9.3s13.2s

General-purpose models maintain near-constant latency.

The Efficiency Inversion

Reasoning models earn their accuracy by spending more time thinking — latency explodes as instruction count grows. General-purpose models stay fast regardless of density.

When you divide accuracy by latency, speed wins:

By AccuracyBy Efficiency
1. o3 / gemini-2.5-pro1. grok-3-mini
2. grok-32. gemini-2.5-flash
3. gpt-4.13. gpt-4.1-nano

Reasoning models take minutes. Smaller models take seconds. For latency-sensitive applications, a fast mid-tier model often wins.

R — Results

Does Quality Hold Up With 500 Instructions?

The Worry

We have seen that models drop instructions, skip the later ones, and stop trying under load. With all of that happening, you might wonder: does the report still make any sense?

If a model has to include 500 keywords, maybe it just stuffs them in and stops writing real sentences. So the paper also measured something beyond accuracy: basic writing quality.

The Answer

For most models, the answer is yes. Report quality stays stable from 10 instructions all the way to 500. Following more instructions does not make the writing worse.

Two Models That Broke the Pattern

o3 and o4-mini were the only models whose reports became noticeably worse as instruction count grew. At high densities, their output stopped reading like a real business report.

Why did this happen? These models produced very few tokens to begin with. o3 wrote only about 1,500 tokens when given 500 instructions. Since 500 of those words had to be keywords, roughly one out of every three words was predetermined — leaving almost no room for normal sentences to form.

An interesting contrast: grok-3 also wrote very few tokens at high densities, but its reports stayed coherent. Same constraint, different outcome — suggesting these two model families handle the tradeoff between instruction-following and writing quality in fundamentally different ways.
D — Discussion

Key Takeaways

Practical guidelines based on what the numbers tell us.

Model Selection

  1. Use reasoning models for heavy prompts. If you need 100+ instructions followed reliably, pick o3 or gemini-2.5-pro. But expect them to be slow.
  2. Use smaller models for light prompts. Below ~50 instructions, small models perform just as well, and they are much faster.
  3. grok-3 hits a sweet spot. Nearly as accurate as o3 (61.9% vs. 62.8%), but faster and more consistent.

Prompt Engineering

  1. Put your most important instructions first. Every model pays more attention to what comes earlier.
  2. But do not rely on ordering alone. Beyond ~300 instructions, even the first ones start getting dropped.

System Design

  1. There is a hard ceiling. Even the best model caps at ~68%. If you need more than that, break the task across multiple calls or agents.
Watch the variance, not just the average. The top models get less consistent as density goes up. High accuracy on one run does not mean high accuracy on the next.
D — Discussion

Limitations

What this paper did not test, and what it did not answer.

What This Paper Did Not Test

  • Only one kind of instruction. Include a keyword. No logical rules, no formatting, no instructions that depend on each other. We do not know what happens when you mix different instruction types at high density.
  • Only one task. Business report writing. We do not know if the same patterns hold for code, chat, or summaries.
  • Only English. Other languages were not tested.
  • Only one vocabulary source. Keywords came from U.S. corporate filings. Results might differ with everyday words.

What This Paper Did Not Answer

  • Why do the three degradation patterns happen? The paper describes them but does not explain the cause.
  • Do these patterns repeat across different tasks and topics?
Future Work

Future Work

From the Paper

  • Investigate degradation mechanisms
  • Explore instruction types beyond simple constraints
  • Generalize degradation curves across tasks
  • Investigate why o3 and o4-mini lose writing quality under high density while grok-3 does not

Personal Directions

  • Extend to evaluate instruction-following across multiple general instruction scenarios

Thank You

Questions?

Appendix

Appendix. Full Results Table

Model1050100250500
claude-3.5-haiku98.078.043.416.68.5
claude-3.7-sonnet100.099.694.872.952.7
claude-opus-4100.0100.094.667.944.6
claude-opus-4 r92.099.681.881.552.1
claude-sonnet-4100.098.094.477.242.9
claude-sonnet-4 r100.0100.094.880.039.9
deepseek-r1 r98.094.886.849.130.9
gemini-2.5-flash100.096.082.050.734.2
gemini-2.5-pro r100.0100.0100.097.767.3
gpt-4.1100.0100.098.484.756.4
gpt-4.1-mini100.0100.097.267.643.2
gpt-4.1-nano100.094.084.037.420.4
gpt-4o100.063.640.014.47.5
grok-3-beta100.0100.099.290.361.9
grok-3-mini98.096.888.027.213.5
llama-4-maverick98.092.868.48.84.2
llama-4-scout100.053.630.810.66.1
o3 r100.0100.0100.097.362.8
o4-mini r100.0100.099.693.052.5
qwen3100.092.087.246.826.9
Appendix

Appendix. Degradation Pattern Reference

PatternCurveKey TraitExamplesBest For
Threshold Flat → steep drop Near-perfect until critical density o3, gemini-2.5-pro High-recall at 100+ instructions
Linear Steady downward slope Predictable across all densities gpt-4.1, claude-3.7-sonnet Predictable tradeoffs
Exponential Rapid drop → floor Overwhelmed early, ~7–15% floor claude-3.5-haiku, llama-4-scout ≤50 instructions only

Variance Behaviors

  • Top models: variance steadily increases — reliability drops, but not yet collapsed at 500.
  • Mid-tier: peaks at 150–300 — a "critical zone" of unstable performance.
  • Worst models: variance drops immediately — already overwhelmed.

llama-4-maverick is an extreme outlier with abnormally high variance, suggesting fundamentally different instruction-processing mechanisms.

1 / 17