acceptodds
Under review as a conference paper at ICLR 2027

MultiSearch: Dynamic Search Tool Orchestration for Intelligent Agents

Abstract

Recent advancements in Large Reasoning Models (LRMs) have enabled agents to perform information seeking involving complex reasoning and planning. Beyond deciding what to search for, agents must also determine which search sources best satisfy their evolving information needs. However, existing agents primarily rely on single general-purpose search engines. Furthermore, selecting suitable source from multiple similar options is far more challenging than distinguishing tools with vastly different capabilities. In this paper, we introduce , a comprehensive benchmark constructed from 319 search sources with overlapping functionality and diverse content coverage. Our analysis reveals a “High Recall, Low Quality” phenomenon: naive retrieval often achieves high recall by matching surface semantics yet fails to translate this into high-quality answers. To address this, we propose a reasoning-based pipeline . Our method treats tool selection as a dynamic planning task and employs a multi-granularity reward mechanism. Extensive experiments at 4B, 8B, and 14B model scales demonstrate that our approach significantly outperforms strong baselines across various metrics. Our work lays the foundation for handling massive similar tools, paving the way for precise source selection in open-ended, multi-source deep research environments. Our code is available at: https://anonymous.4open.science/r/MultiSearchhttps://anonymous.4open.science/r/MultiSearch.

Primary area:
datasets and benchmarks
Keywords:
Information Seeking, Deep Search Agent, Tool Orchestration

Reviews

Among:
Shape:
1234this paper, Top 49%
Figure 1. Mean review rating of the reviewed papers at ICLR 2027. This paper averages 2.33 over 3 reviews, above 51% of the others.
Reviewer_Nv9yOpenReview ↗
Rating
3(+1)
Confidence
3
Informativeness
2
Presentation
3
Soundness
2
Read review
Paper summary

The paper introduces MultiSearch-Bench (319 search sources; 1,000 tasks) and MultiSearch-R, which combines abstract tool descriptions, retrieval, dynamic tool/query selection, and iterative evidence synthesis with multi-granularity GRPO rewards. Experiments at 4B, 8B, and 14B report strong final-answer scores.

Critical strengths
  1. Fine-grained selection among overlapping search sources is practically important.
  2. The paper provides a dedicated benchmark, several model scales, stage-wise analyses, and significance tests.
Critical weaknesses
  1. At 8B, removing the planning reward, execution reward, or requirement analysis changes the answer score only from 0.862 to 0.855/0.851/0.857 (Table 12). Evidence summarization also has a large impact (Table 11), leaving the main source of the gains unclear.
  2. GPT-4o-mini is used for both response rewards and primary evaluation, yet its scores exceed human ratings by 2.242/10 on average, with a CCC of only 0.290 (Table 10). Independent cross-baseline evaluation is missing.
  3. Only 10 of 319 sources use custom wrappers; the others largely rely on domain-restricted search. The test split has 100 examples, including only 20 multi-source tasks.
Questions for authors
  1. Can the strongest baselines be evaluated with matched evidence summarization, search budgets, and generation settings?
  2. Can Claude/Gemini or blinded human evaluation verify the final-answer gap against the strongest baseline?
Reviewer_4u2pOpenReview ↗
Rating
2
Confidence
3
Informativeness
2(+1)
Presentation
3
Soundness
3(+1)
Read review
Paper summary

The paper studies how search agents should choose among many functionally similar search sources. It introduces MultiSearch-Bench (1,000 tasks over 319 sources) and MultiSearch-R, a plan-retrieve-select-summarize pipeline trained with GRPO using planning, execution, and answer rewards, which outperforms Search-o1, Search-R1, and WebThinker at 4B-14B scales.

Critical strengths
  1. The problem of choosing among similar search sources is practical and underexplored.

  2. The benchmark covers a broad range of sources and caches trajectories and pages for offline replay.

  3. The evaluation covers tool selection, query quality, answer quality, and cost, with the LLM judge checked against humans.

Critical weaknesses
  1. The experiments are surprisingly limited: the main text has a single results table, only on the authors' own benchmark with about 100 test instances. Reviewers are not obliged to read the appendix, so the main paper must support its claims on its own.

  2. The baselines and related work are outdated, with the benchmark comparison relying mainly on 2023 work (Toolformer, ToolkenGPT, ToolLLM). Table 1 omits widely used agent harnesses such as Codex or Claude, even though Claude Sonnet 4.6 in the authors' own pipeline already beats all trained MultiSearch-R models (0.919 vs. at most 0.875).

  3. The novelty is unclear: the plan-retrieve-select-execute pipeline is now standard, and even if a genuine novelty exists, the authors fail to highlight it. Their own ablations change the answer score by less than 0.01 when requirement analysis or the planning reward is removed.

Questions for authors

Null

1 comment

Thank you for the response. My W1 remains unaddressed as the authors did not provide experiments beyond its own benchmark and I see no revision of moving more experiments into the main paper (still in Appendix). In recognition of the authors' effort, I will increase the informativeness and soundness score.

Reviewer_EALROpenReview ↗
Rating
2
Confidence
3
Informativeness
2
Presentation
2
Soundness
2
Read review
Paper summary

This paper studies the problem of selecting appropriate search sources from a large collection of tools with overlapping functionality. The authors introduce MultiSearch-Bench, a benchmark comprising 1,000 tasks constructed from 319 search sources, and MultiSearch-R, an iterative search framework that generates abstract tool descriptions, retrieves candidate tools using dense retrieval, selects tools and formulates queries, and synthesizes the retrieved evidence. The framework is trained using GRPO with planning, execution, and response-level rewards.

The authors report improvements in final-answer quality across 4B, 8B, and 14B model scales compared with several internal baselines and existing search agents. They further identify a “High Recall, Low Quality” phenomenon, where strong tool-retrieval performance does not necessarily translate into high-quality final answers.

I find the problem relevant, and the focus on selecting between search sources with overlapping functionality is potentially useful. The benchmark and end-to-end implementation are meaningful engineering contributions. However, I have several concerns regarding the distinction from closely related work, the validity of the benchmark setting, the attribution of the reported improvements to the proposed method, and the reliability of the primary evaluation metric. In particular, some of the paper's own diagnostic experiments suggest a more limited explanation of its improvements than the main claims imply.

Critical strengths

Relevant problem setting. The paper focuses on fine-grained search-source selection rather than conventional tool selection between functionally distinct APIs. This is an interesting practical problem, particularly as agents increasingly interact with specialized information sources.

End-to-end benchmark and implementation. MultiSearch-Bench provides a concrete evaluation environment with 319 sources and both single-source and multi-source tasks. The paper also integrates source discovery, query formulation, evidence retrieval, and answer generation into a working pipeline.

Useful empirical diagnostics. The authors go beyond overall answer scores by evaluating tool selection, query quality, search activity, and evidence processing. The stage-wise experiments in Appendix F are particularly valuable in understanding where performance differences arise.

Efforts toward evaluation robustness. The paper includes statistical significance testing, alternative tool-selection metrics, additional LLM judges, and human evaluation. These are useful efforts, although the results also raise concerns discussed below.

Critical weaknesses
  1. Limited methodological novelty relative to closely related tool-discovery and planning work

The main methodological contribution appears incremental relative to existing approaches to agentic tool discovery and iterative retrieval.

In particular, MCP-Zero (Fei et al., 2025), which the paper cites, already explores proactive tool discovery through descriptions of required tools and retrieval from a large tool repository. More recent work such as ToolQP (Fang and Glass, 2026) also studies iterative tool-query planning and reinforcement learning for improved tool retrieval.

MultiSearch-R similarly generates abstract descriptions of desired tools, maps them to concrete tools using a dense retriever, and iteratively selects tools and executes queries. The multi-granularity reward formulation combines tool-selection accuracy, semantic relevance of retrieved evidence, and final-response quality.

While the application to search sources is distinct, the paper does not sufficiently establish what fundamentally new methodological capability is introduced beyond adapting these existing ideas to a particular tool environment. The reward formulation also seems to combine relatively standard intermediate and outcome-level signals rather than introduce a clearly new optimization principle.

The more distinctive contribution may therefore be the benchmark and its focus on search-source overlap, rather than the proposed planning or RL method.

A direct comparison with adapted tool-discovery and iterative retrieval-planning approaches would be important for establishing the incremental contribution of MultiSearch-R. The comparisons with Search-o1, Search-R1, and WebThinker are useful but do not fully answer this question, since these systems were not necessarily developed for source selection from a large repository of similar tools.

  1. Benchmark construction raises concerns about realism and what is actually being evaluated

MultiSearch-Bench is constructed by first collecting evidence from selected websites and subsequently generating questions and reference answers from that evidence. This ensures that the questions are answerable from the collected documents, but it introduces two important limitations.

First, the generated questions may reflect the characteristics of the originating sources rather than naturally occurring information needs. Second, the reference tool set identifies the sources used during benchmark construction, not necessarily all sources capable of answering the question correctly. This is particularly relevant in a benchmark explicitly motivated by overlapping source functionality.

The paper does consider category-level and subcategory-level alternatives to exact tool matching, which partly addresses this concern. Nevertheless, the main rewards and tool-selection evaluations continue to rely heavily on the originating reference sources.

There is also an important distinction between the claimed search-tool orchestration setting and its implementation. Appendix A.3 indicates that only ten platforms have custom search wrappers, while the remaining sources are accessed through Google-backed domain-restricted search. Consequently, most of the benchmark evaluates selecting websites or search domains under a largely shared search backend, rather than selecting among genuinely heterogeneous search tools with different native query capabilities.

This is a reasonable controlled setting, but it is narrower than the broader search-tool orchestration problem discussed in the introduction.

Finally, the benchmark contains 800 single-source and 200 multi-source tasks, corresponding to only 20 multi-source examples in the reported 100-example test split. Since multi-source orchestration is central to the motivation, aggregate results alone are insufficient to establish how well the method handles the most relevant cases.

It would be helpful to report separate results for single-source and multi-source tasks, evaluate tasks independently written from real user information needs, and quantify the difficulty introduced by semantically similar but factually unsuitable sources.

  1. The experiments do not adequately isolate the source of the final-answer improvements

The reported final-answer improvements are substantial, but it is not clear how much of the improvement is attributable specifically to the proposed reasoning-based tool-selection mechanism.

The ablation results in Appendix Table 12 are informative. On the 8B model, removing the planning reward reduces the final-answer score from 0.862 to 0.855; removing the execution reward reduces it to 0.851; using only the sparse outcome reward yields 0.852; and removing requirement analysis yields 0.857.

These ablations show larger differences in reference tool F1 than in final-answer quality. For example, removing requirement analysis changes the final-answer score by only 0.005. Without uncertainty estimates for these particular differences, it is difficult to determine how much evidence they provide for the importance of the individual components to the final outcome.

More importantly, the stage-wise diagnostics in Appendix F suggest that downstream evidence processing is a major source of improvement.

For the 8B model, replacing the naive retrieval baseline's candidate tools with reference tools increases its answer score only from 0.5247 to 0.5390. In another diagnostic configuration using reference URLs, replacing truncated raw evidence with two-stage summaries raises the score from 0.6007 to 0.8343.

These results are valuable, but they suggest that evidence representation and summarization may explain a substantial portion of the observed performance gap. Since the diagnostic configurations vary multiple aspects of the pipeline, they do not provide a clean causal decomposition.

I would like to see a controlled comparison in which a strong baseline uses the same webpage extraction, summarization, answer-generation procedure, and comparable inference budget as MultiSearch-R, differing primarily in its tool-selection and planning strategy.

Without such comparisons, the experiments establish that the integrated system performs well, but provide weaker evidence that reasoning-driven source planning is the principal reason for its advantage.

  1. Concerns regarding the reliability and independence of final-answer evaluation

This is my most substantial concern regarding the reported quantitative results.

The paper uses GPT-4o-mini extensively for benchmark generation, reference-answer generation, webpage summarization, response rewards, and final-answer evaluation. Using an LLM judge is not inherently problematic, but the degree of overlap between training and evaluation makes independent validation particularly important.

The authors conduct additional human and LLM-judge comparisons in Appendix E. However, Table 10 reports a mean positive bias of 2.242 and a concordance correlation coefficient of only 0.290 for GPT-4o-mini relative to human evaluation. By comparison, Claude Sonnet 4.5 and Gemini 2.5 Flash achieve concordance coefficients of 0.802 and 0.769, respectively.

These findings raise a significant calibration concern for the judge used to produce the principal final-answer scores. Correlation with human judgments is not equivalent to absolute agreement, and a systematically lenient judge may not preserve the magnitude of performance differences between systems.

The reported validation also appears focused on answers generated by MultiSearch-R rather than a balanced evaluation of the competing methods. Consequently, it is not clear whether the primary judge evaluates all methods with comparable reliability.

The key-point-based evaluation further measures agreement with LLM-generated reference answers, which is not necessarily equivalent to independently verified factual correctness or evidence grounding.

I would strongly encourage the authors to reproduce the principal comparisons using independent judges and blinded human evaluations across all major methods. Given the reported calibration results, this is important for interpreting the headline answer-quality gains.

  1. Several conclusions are stronger than the experimental evidence supports

The paper places considerable emphasis on the “High Recall, Low Quality” phenomenon. The reported observation is useful: for example, at the 8B scale, Multi Search Filter achieves higher tool-selection F1 than MultiSearch-R (0.5810 versus 0.4873), but much lower final-answer quality (0.5247 versus 0.8623).

However, the broader observation that retrieval accuracy does not necessarily translate into downstream task success is already well established in retrieval and tool-use research. The novelty here would lie in explaining the phenomenon specifically for overlapping search sources.

The current experiments do not fully establish that explanation. In fact, Appendix F suggests that evidence acquisition and processing may be at least as important as the source-selection mechanism. I therefore find the empirical observation convincing within the benchmark, but the interpretation that it establishes the necessity of the proposed reasoning-driven planning approach is less convincing.

Similarly, the claims regarding improved efficiency require qualification. While search calls and iteration counts decrease after training at the larger model scales, reported output-token consumption increases across all three scales. The paper also does not provide a comprehensive account of latency or total operational costs, including the summarization and retrieval components.

Finally, the paper motivates its approach in terms of open-ended, multi-source deep research. However, the benchmark consists primarily of questions generated from predefined evidence with corresponding reference answers. This does not fully test research settings involving conflicting evidence, uncertain conclusions, source credibility, or genuinely open-ended synthesis.

I would recommend framing the conclusions more narrowly around the demonstrated source-constrained question-answering environment.

  1. Presentation and technical clarity

The paper is generally understandable, and the overall pipeline is clearly presented. Nevertheless, several claims could be stated more precisely.

In particular, expressions such as “paradigm shift,” “unexplored question,” and “paving the way” overstate the scope of the contribution relative to existing research.

The discussion of judge reliability also needs revision in view of the poor absolute agreement reported for GPT-4o-mini. There are minor grammatical and editorial issues throughout, and some implementation details would benefit from clearer specification.

These are secondary concerns relative to the experimental and methodological issues above, but improving the precision of the writing would make the actual contribution easier to assess.

Questions for authors

Novelty and baselines: How does MultiSearch-R differ substantively from MCP-Zero and more recent iterative tool-query planning approaches? Can the authors compare against an adapted iterative tool-retrieval baseline under identical execution and evidence-processing conditions?

Attribution of improvements: Given the relatively small final-answer differences in Appendix Table 12 and the large summarization-related difference in Appendix F, can the authors provide a controlled factorial ablation that isolates planning, tool retrieval, query formulation, evidence summarization, and RL training?

Benchmark difficulty: What proportion of test tasks genuinely require fine-grained discrimination between highly similar search sources? Can the authors quantify source overlap and provide performance breakdowns by source similarity and single-source versus multi-source tasks?

Search environment: How well do the conclusions generalize beyond Google-backed domain-restricted search to sources with independent retrieval engines, structured query interfaces, and proprietary indexed content?

Statistical robustness: Are the answer-quality differences in the reward and requirement-analysis ablations statistically significant across evaluation instances and training seeds? How sensitive are the findings to the reward coefficients and choice of evaluator?

From OpenReview, CC BY 4.0. Authors as signed there; shown unedited.

Related papers

Loading the map…

Discussion (0)

Sign in to comment.