Skip to content
ML Academy

LLMs, GenAI, RAG, agents, evaluation · insight-0502

Test effective context at your own input lengths instead of trusting the advertised window

Evidence type
empirical finding
Difficulty
medium
Roles
Applied AI, ML engineer
Industries
aviation, cross-industry

Summary: situation, action, reason, boundary

  1. Situation

    A team plans to paste a whole ground-handling contract (a hypothetical 300 pages) into one prompt because it fits inside the documented context window.

  2. Action

    Build a probe set with known answers placed at different depths and at production-like lengths, including questions that combine several facts, and measure accuracy by length and position before choosing whole-document prompting over retrieval.

  3. Reason

    Long-context studies report accuracy falling as inputs grow and depending on where the relevant text sits, so usable context is shorter than the maximum accepted input.

  4. Boundary

    Contract review, long-document Q&A, log analysis, multi-document summaries.

Symptom or risk

Answers miss clauses buried in the middle or mix up similar clauses, while everyone assumes that anything inside the window is used.

Exceptions

Inputs far below the window rarely need probing; a newer model may degrade less, which the probe will show.

Trade-offs

A day of probing versus silent misses found later by users.

Pitfalls

Testing only single-needle lookups, which are easier than multi-fact reasoning over long inputs.

Lessons and concepts

Claims and their sources