Key points
- Repeated summarization turns numbers, percentages, dates and customer-stated expectations into vague phrases.
- Models attend reliably to the start and end of a long input and may skip the middle ("lost in the middle").
- Tool results accumulate out of proportion to their value: one lookup can return dozens of fields when a handful matter.
- Every call must carry the complete conversation history; the model remembers nothing between calls.
- A "case facts" block holds transactional facts (order ids, amounts, dates, statuses) outside the summarized history and is sent with every prompt.
- Trim tool output to the relevant fields before it enters the conversation.
- Put a key-findings summary first and organize details under explicit headers when aggregating long inputs.
Common misconceptions
- "A bigger context window solves it." The position effect and summarization loss remain; the window only delays them.
- "Telling the model to be precise with numbers is enough." Compression loses detail regardless of instructions.
- "Sending only the latest message is cheaper and fine." It breaks coherence and causes repeated lookups.
Watch for
Answer choices that fix a cost problem by summarizing harder, or a memory problem by resending everything. The best answer usually moves a small set of exact facts into a protected place and removes waste at the source.
Practice Task 5.1
Start with the free 10-question check to see where you stand across all five domains. In CCA Prep Studio, 57 practice items cover this task, each tracked toward your mastery score.