Summary
The paper studies two framework which uses LLM for planning. In the first framework, one uses a classical planning algorithm to search solutions whilst relying on an LLM as a heuristic to explore promising states and propose actions. The second is to use an LLM as a generative planner directly, proposing a sequence of actions (i.e., plan) and getting feedback from the world model.
The paper found that empirically, using LLM as a generative planner is more query efficient. That is, it uses fewer queries to the world model during the planning process to find solutions. The paper provides extensive experimental results to justify its claims. In addition, the paper shows various failure modes for different methods, showing that using LLM as a heuristics doesn't allow it to explore totally different states in cul-de-sacs situations, as compared to LLM as a generative planner, which can switch to entirely different plans straightaway.
Strengths
1. The paper is easy to read, because the main idea is quite straightforward (using LLMs as a heuristic or generative planners are arguably known methods which have been used in prior papers).
2. The experiments are well conducted and extensive. They are broken down such that each question can be answered directly from a figure/table.
3. Failure modes are shown in the paper to corroborate each method's contribution and capabilities.
Weaknesses
1. The main idea and motivation of the paper is quite simple. While this is not really an issue per se, I feel that there are several places in the paper where contributions are overclaimed. (a) The abstract mentioned that "we propose and study two fundamentally competing frameworks ... the first uses LLMs as a heuristic within a search-based planner to select promising nodes to expand and propose promising actions ... the second uses LLMs as a generative planner". However, I am quite sure this paper is not the first to propose these two frameworks. For example, [1,2] all uses a LLM as a heuristic in one way of another to expand the search tree (or propose actions) and [3] uses LLMs to propose candidate plans. (b) the paper also claims to have introduced Tree of Interaction (TOI), which " ... maintains a search tree and invokes the LLM to choose which states to expand and what actions to propose". However, similar approaches have been proposed in prior works [1]. Therefore, I'd suggest the author making it clearer what the novel contribution of the paper is. Perhaps, the intention of the paper is to study the two frameworks from a query-efficient point of view?
2. In light of the point above, I feel the paper's proposed methods are not sufficiently novel. The paper's writing should reflect the novel parts clearly (for example, [1,2] have all used LLM as heuristic to expand the search tree, so can we really consider TOI, which does the same, a novel contribution?).
3. The paper claims that using LLM as a generative planner (Boomerang) needs to query the world model fewer times. In the boomerang setting, we would need to pass in the entire proposed sequence of actions (the entire plan) into the world model each time. On the other hand, for TOI, we need to simply pass in a single action at each planning stage. While the results show that Boomerang queries the model fewer times in total, at each stage the world model might incur larger computational cost because it needs to handle an entire sequence of actions. Shouldn't this be taken into account before discussing about query-efficiency? Would a metric such as time taken be better?
[1] Yu. et, al. Prompt-Based Monte-Carlo Tree Search for Goal-oriented Dialogue Policy Planning, 2023
[2] Hui. et, al. RoT: Enhancing Large Language Models with Reflection on Search Trees, 2024
[3] Kambhampati. et, al. LLMs Can't Plan, But Can Help Planning in LLM-Modulo Frameworks, 2024
Questions
Line 403: There is random dot on the paper.
Line 373: Citation formatting is incorrect
Figure 2 & 4 seems to show the success rates of various algorithms on PlanBench. What is the difference between the two figures? Also, for some reason the same algorithm is giving different performance in both plots?