Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort."
HFEPX · Eval paper review
Xuanming Zhang, Amir H. Rezaeian, Miguel Ballesteros, Weiyi Sun +5 more
Published
Oct 17, 2026
Citations
0
Trust level
Low
Usefulness score
0/100 (Low)
Extraction confidence
35% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Oct 17, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
All signals on this page are inferred from the abstract only and may be inaccurate. Do not use this page as a primary protocol reference.
Best use
Background context only
Use if you need
A secondary eval reference to pair with stronger protocol papers.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
This paper looks adjacent to evaluation work, but not like a strong protocol reference.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort. Existing evaluations typically measure this burden by counting questions, treating necessary and avoidable questions equally. We propose an evaluation protocol that distinguishes how often agents ask from how well they ask. An interruption budget limits the number of questions, while a user-attention cost charges extra for questions that are hard to read or not worth asking, as rated by a human-validated LLM judge. Beyond question counts, this cost captures perceived effort: on conversation pairs with the same number of questions, human annotators agreed with the cost on which conversation required more effort 75% of the time. Across eight LLMs and four customer-service domains, limiting agents to one to three questions reduces user-attention cost by 36-73% while keeping 86-94% of the task reward they earn with unlimited questions. At the same budget, reviewing each question against the memory of users' earlier answers cuts attention cost by another 13% with little reward loss and yields more valuable questions. Models also differ sharply in how well they ask: at the same user-attention cost, the most efficient models gain more than twice as much reward from their questions as the others. These results show that asking less and asking better are distinct goals, and that evaluations of proactive agents should measure both.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
None explicit
No explicit feedback protocol extracted.
"LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort."
Automatic Metrics
Includes extracted eval setup.
"LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort."
Not reported
No explicit QC controls found.
"LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort."
Not extracted
No benchmark anchors detected.
"LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort."
Not extracted
No metric anchors detected.
"LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
LLM agents can ask clarifying questions to complete tasks, but answering each question demands users' time and effort.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
No explicit human feedback protocol detected.
Evaluation mode is explicit
Detected: Automatic Metrics
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.