Sep 2026· Radio Electronics Computer Science Control
Abstract
Context. The problem of comparative evaluation of communication protocols for task orchestration by large language model (LLM) agents is considered. The object of study is the process of interaction between LLM agents and external tools, as well as between autonomous LLM agents, during task orchestration.Objective. The goal of this work is to develop a systematic pilot benchmark comparing tool integration, multi-agent delegation, and hybrid architectures for standardized queries at three levels of complexity, and to quantify the advantages and disadvantages in terms of response time, context window consumption, cost, error recovery, and implementation complexity.Method. An open-source health analyzer application was developed to query four public data sources for repository statistics, package downloads, vulnerability data, and community metrics. Thirty queries were run five times for each architecture at three levels of complexity, resulting in 450 fail-safe executions. The same large language model was used in all executions. The statistical analysis used bootstrap confidence intervals, the Mann-Whitney test with Bonferroni correction, and Cliff’s delta effect sizes.Results. A statistically significant crossover effect was found: the tool integration protocol is faster for simple queries, but the multi-agent protocol outperforms on complex multi-project comparisons, consuming fewer tokens through distributed context windows, resulting in lower cost. The hybrid architecture tracks the winner at each level of complexity with near-optimal performance.Conclusions. The scientific novelty is an empirical demonstration that the two protocols exhibit a complexity-dependent performance crossover, showing that they complement each other rather than compete. Context-window bloat in single-agent architectures is quantified for the first time in a pilot case study. The practical significance is a validated decision framework: using a tool integration protocol for single-source queries, a multi-agent protocol for complex orchestration, and a hybrid routing when complexity is unknown at runtime. Directions for further research include extending the benchmark to additional models, distributed deployments, and additional application domains
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.
P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al.· IEEE International Conferenc...· 110 citations· ⚡7
The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· International Conference on...· 84 citations· ⚡6
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026