Consider this simple, stylized example that illustrates the distinction:
User query: “Who was Galileo Galilei?”
Context: “Galileo Galilei was an Italian astronomer.”
Model response: “Galileo Galilei was Italian.”
Analysis: This response would receive a perfect Context Adherence score: everything the model said is supported by the context. But this is not an ideal response. The context also specified that Galileo was an astronomer,
and the user probably wants to know that information as well. Hence, this response would receive a low Completeness score.
Tracking Completeness alongside Context Adherence allows you to detect cases like this one, where the model is “too reticent” and fails to mention relevant information.
Track completeness scores across different types of content and queries to identify patterns where information is consistently omitted.
Balance with Conciseness
Find the right balance between completeness and keeping responses concise and focused for your specific use case.
Combine with Other Metrics
Use completeness alongside context adherence, correctness, and relevance metrics for a comprehensive view of response quality.
Test with Complex Queries
Evaluate completeness with complex, multi-part queries that require synthesizing information from multiple context sections.
When optimizing for completeness, be careful not to encourage your model to include irrelevant information just to achieve higher scores. The goal is to include all relevant information while maintaining focus on the user’s query.