- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper discusses the idea of sufficient exposure of an agent request, backing it up experimental results. Further, to reduce token cost and improve agent's ability, the paper proposes LeanCalw to estmate sufficient exposure and control the exposed context.
Critical strengths
- The proposed LeanClaw shows great empirical improvement across the benchmarks, saving significant amount of tokens while maintaining or improving task performance.
Critical weaknesses
- Most details about the proposed algorithm is not clearly described in the paper. (Examples in the questions) I expect the details are contained in the provided codes but I cannot access it from the provided link. Even with codes provided, clear disclosure of procedure details would be necessary for readers to understand what's happening and evaluate the novelty of the proposed method.
Questions for authors
- For the initial exposure and , how are they decided?
- What does the procedure do?
- How is the controller's confidence defined? How is the threshold decided?
- As I understand, modifying the toolset at each round effectly change the input prompt and may make the cache invalid. Will this impact the cost of the provided method? If so, is this impact taken into account when calculating all the costs in the paper?
3 comments
Thank you for your rebuttal. For the latest revision, the pdf file does not look like ICLR submission format. Please confirm that the uploaded PDF follows the ICLR submission requirement.
Thank you for pointing this out. We have corrected the formatting and regenerated the PDF using the official ICLR 2027 submission template. We hope that these corrections address your concern and will support a favorable reconsideration of our submission.
Best regards,
Authors
Weakness 1: Algorithm and code accessibility
Thank you for flagging both the link and disclosure issues.
Response: We rechecked the anonymous repository link and confirmed that it is accessible. The code is also included in the supplementary attachment, so the implementation is available through two routes.
Question 1: How are Initial Exposure and Exposure Profile Determined?
Thank you for asking how initial exposure is determined.
Initial exposure comes from the task-conditioned tool prior. When the planner is enabled, it returns the necessary tools and budget points; deterministic normalization then supplements tools based on task risk guards. If the planner is ineffective, deterministic seed rules are used, and fail-open is triggered when confidence is low. Afterward, the exposure profile continues to update based on execution status and feedback, rather than remaining fixed after the first request.
We will include a detailed trace in the appendix showing the task text, initial tool set, feedback signals, updated exposure set, and runtime tool registry.
Question 2: What exactly does the
Adaptprocess do?Thank you for requesting a concrete account of
Adapt.Adapttranslates the current task, interaction messages, execution status, and available tool list into the next model-visible exposure decision. It selects or retains tools based on the matching task or feedback signals at the current stage, recording added, removed, and retained tools and confidence; fail-open is triggered when selection is empty or below the threshold. This process only filters the provider-facing schema view and does not remove tools from the runtime registry or execution bridge.We will replace the current overly abstract description with pseudocode and decision tables, and clearly define the boundaries between the planner-driven and deterministic guard parts.
Question 3: How is Confidence defined, and how is the threshold determined?
Thank you for asking about the score and threshold.
In the current deterministic selector, confidence is a score truncated to 1 after dividing the number of matched tasks or execution signals by 3. The default threshold is 0.25. When the score is below the threshold or the selection is empty, the system uses a wider fail-open exposure.
Question 4: Cache-aware cost.
Thank you for highlighting the potential cache effect.
Changing tool patterns or retaining historical records can affect the prefix cache, so simply reducing the number of tags is insufficient to demonstrate cost savings. We report the number of cached and non-cached input tokens recorded by the provider, along with billing costs, including LeanClaw's planner calls:
In this RealClawBench full281 run including caching, LeanClaw's token-level cached input share was 48.92%, while OpenClaw's was 46.95%. Therefore, the observed aggregate cache share did not decrease. Total provider tokens decreased by 48.63%, while provider-reported cost decreased by 47.56% after accounting for planner overhead. For the cached/uncached token breakdown and cost comparisons across benchmarks, see our response to Weakness 1: Cache-aware inference costs.