Papers › HumanEvalComm: Benchmarking the Communication Competence of Code Generation for LLMs...

HumanEvalComm: Benchmarking the Communication Competence of Code Generation for LLMs and LLM Agent

31 May 2024arXiv:2406.00215links table onlyarchive 2025-07-28

Jie JW Wu, Fatemeh H Fard

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Large language models (LLMs) have significantly improved their ability to perform tasks in the field of code generation. However, there is still a gap between LLMs being capable coders and being top-tier software engineers. Based on the observation that top-level software engineers often ask clarifying questions to reduce ambiguity in both requirements and coding solutions, we argue that the same should be applied to LLMs for code generation tasks. In this work, we conducted an empirical study on the benchmark and analysis of the communication skills of LLMs for code generation. We define communication skills of LLMs as ``being able to ask clarifying questions when the description of the code generation problem has issues''. We created a new benchmark, HumanEvalComm, by modifying problem descriptions according to three issues: inconsistency, ambiguity, incompleteness. We defined new evaluation metrics such as Communication Rate and Good Question Rate, and then experimented on HumanEvalComm with different Code LLMs, and a new LLM agent approach, Okanagan, to identify and ask questions in ambiguous parts from code and descriptions for further refining the generated code. Finally, we discussed evaluation results by comparing Code LLMs and Okanagan with our findings.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 19 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 7 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 19 samples from 1 repository, 12 ran (7 with no instrument failure; 5 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

jie-jw-wu/human-eval-comm officialmentioned in papermentioned on GitHubSyntology: 19 samples, 12 ran (5 instrument-failed) · 7 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

19 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
4ran · our draft was wrong
1ran; the contract check could not run
5ran
7unverified

Licence: 19 of the 19 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from jie-jw-wu/human-eval-comm. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

jie-jw-wu/human-eval-comm official repository 19 samples, 12 ran (5 instrument-failed) · 7 unverified
extract_prefix measurement_summary_draw_heatmap.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 0bf323d93f03b832 · report fixture: signature string:str/0/str · returned str · level recorded 2026-09-24
generate_text in 20 papers generate_response.py ran no licence file found · pointer only · 7f8144a905f5b101 · report fixture: signature model:callable/0/?, tokenizer:callable/0/?, prompt_text:str/0/str, args:Args/0/?, eos_token_id:NoneType/0/? · returned list · level recorded 2026-09-24
get_ask_question_rate syntactic_similarity_OER.py ran · honoured contract fingerprinted no licence file found · pointer only · 5dba7da2cfd89116 · report fixture: signature input_string:str/0/str · returned int · level recorded 2026-09-24
get_ask_question_rate_with_qq syntactic_similarity_OER.py ran · honoured contract fingerprinted no licence file found · pointer only · b088fc0024baa28f · report fixture: signature question_quality:int/0/int · returned int · level recorded 2026-09-24
preprocess_data in 44 papers AgentFramework/designer.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 491a124a37148dfd · report fixture: signature test_case_string:str/0/str · returned str · level recorded 2026-09-24
preprocess_data in 44 papers AgentFramework/executor.py ran no licence file found · pointer only · b231819920453b1d · report fixture: signature task:dict/0/?, lg:str/0/str · returned dict · level recorded 2026-09-24
preprocess_data in 44 papers AgentFramework/programmer.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 854e64377cfc300a · report fixture: signature completion_string:str/0/str · returned str · level recorded 2026-09-24
programmer_main AgentFramework/programmer.py ran no licence file found · pointer only · 2e3b2a31d4b30e77 · report fixture: returned list · level recorded 2026-09-24
ratio_of_worst measurement_summary_draw_heatmap.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 3a8a940a00b74328 · report fixture: signature list:list/1/int, target:int/0/int · returned float · level recorded 2026-09-24
response_2_code intermedia_analyze.py ran · our draft was wrong fingerprinted no licence file found · pointer only · ed2c1ad3bc24cdc8 · report fixture: signature response:str/0/str · returned str · level recorded 2026-09-24
solution_evaluation intermedia_analyze.py ran no licence file found · pointer only · 44d500098cd18911 · report fixture: signature solution:str/0/str, test_cases:list/1/dict, demo_file:str/0/str, time_limit:int/0/int · returned tuple · level recorded 2026-09-24
solution_evaluation_HumanEval intermedia_analyze.py ran no licence file found · pointer only · cd60fe0a3a7d62ad · report fixture: signature solution:str/0/str, test_cases:list/1/dict, demo_file:str/0/str, call_demo_file:str/0/str, entry_point:str/0/str, time_limit:int/0/int · returned tuple · level recorded 2026-09-24
analyze_among_top0_5 syntactic_similarity_OER.py unverified no licence file found · pointer only · 509467404a76b343 · report
designer_main AgentFramework/designer.py unverified no licence file found · pointer only · 310e25d69d224637 · report
fetch_completion AgentFramework/designer.py unverified no licence file found · pointer only · c8ae809824048769 · report
fetch_completion AgentFramework/programmer.py unverified no licence file found · pointer only · 19a9b628e7fcf1e1 · report
get_completion_starchat_nl_to_pl generate_response.py unverified no licence file found · pointer only · e5fc7b939577a999 · report
get_completion_starchat_pl_to_nl generate_response.py unverified no licence file found · pointer only · 1fcf5236ce19bc6e · report
semantic_syntactic_structural_similarity measurement_summary_draw_heatmap.py unverified no licence file found · pointer only · 5eef0e3253e15ffa · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections