From 3d39685afa0a8a021c386e78233185cf342caf3a Mon Sep 17 00:00:00 2001
From: Phil Bajsicki <phil@bajsicki.com>
Date: Mon, 28 Apr 2025 20:09:44 +0200
Subject: [PATCH] Update README.org

---
 README.org | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/README.org b/README.org
index c033e50..9792542 100644
--- a/README.org
+++ b/README.org
@@ -470,17 +470,13 @@ My journal is a single file, with a hierarchy like so:
 ,*** [YYYY-MM-DD Day HH:MM])
 #+end_src
 
-I wanted to make sure that if I asked about a time period, the LLM would be able to pull at least roughly around the right time from my journal, without blowing out its context window.
+This tool /kinda sorta/ works. It has two main failure modes:
+ 1. the LLM chooses to apply this tool to buffers other than my journal.
+ 2. the LLM ignores the existence of this tool and instead uses regexp with terms... and explodes the context window.
 
-This /kinda sorta/ works. The only time I have seen this fail is when the LLM chooses to apply it to buffers that don't follow that convention.
+The reason for this tool existing (it's the same as select-heading), is that it may help guide the LLM toward higher accuracy. Unclear if that's the case.
 
-I doubt it'll be useful for anyone else, but it's here and fairly easy to adapt to other needs.
 
-Notice it pulls to the end of the subtree. So for months, that's at least 28 entries, and during busy months, possibly hundreds.
-
-But, any customizations to tweak this is left to the user, as everyone has their own conventions.
-
-Testing new version:
 #+begin_src elisp
 (defun gptel-org-tools--org-ql-select-by-date (buf date)
   "Returns all timestamped headings matching the specified date or date range.