Tokens = fuel. Your prompt runs on this. The diagram shows a tank (context window) feeding a model, with three output paths: full (clear), low (degraded), empty (cut off). Footer: more ≠ better. The metaphor is blunt on purpose — operators confuse having fuel with pouring in the wrong fuel.
Full — the right context, not the max context
Full means the run has what the task needs: policy version, scoped retrieval, output contract, checker rules — without drowning signal in noise. Teams hit “full” with curation, not with exports of every PDF in the drive.
Low — degraded but tempting
Low fuel is “we probably gave enough.” Format slips; citations thin; tone wanders. This is where pilots feel “good enough” until a regulated field errors. Low is a warning to split steps or tighten retrieval — not to bump temperature for creativity.
Empty — cut off and dangerous
Empty is not only literal token exhaustion. It is missing policy, missing CRM context, missing denial rules — while the model still produces text. Cut-off outputs fail quietly in busy queues.
More tokens is not more control
Buying capacity without governance increases cost and hallucination surface. Pair this visual with Tokens and Context Window Limits for overflow mechanics and Memory Types for AI Systems for what should not sit in every run’s tank.
Go deeper
Fuel without an engine map wastes money. The Model Is Not the System shows where generation sits in workflow — and who owns refueling (context updates) over time.