Hello,

What is the intent of the userQuery param being added to get-library-docs in #222 ?

This change in behavior concerns me with agents possibly sending more information than I would like to send to a party whose privacy policies / data retention policies I have not yet reviewed, and cannot find any documentation as to why the change is being implemented and for what reason. Before this change I was rather comfortable using the library as-is as all it did was a discovery, then a fetch of the library documentation passing along specific topics.

However, now the addition of a user query parameter with prompting specifically stating the agent to provide the original user query as is, without changing it, concerns me with data leakage potential from my agents. Especially because my workflow, and likely many others who use the library constantly, set these tools specifically to be trusted.

I am curious to what the intent of this change in behavior is? For now I've just decided to fork for my own usages, but curious if you could share the intent of the change. Thanks.