docs(rfd): Draft configurable tool parameter visibility - #1021
Open
JeanMertz wants to merge 2 commits into
Open
Conversation
A tool parameter is either in the JSON schema for every conversation or it does not exist. A parameter that is useful in one context and noise in the rest has nowhere to live: declaring it unconditionally makes every conversation reason about an argument it will rarely use, and moving it to `options` takes the choice away from the model entirely. The draft adds `enabled` to a parameter's configuration, so a config layer can hide a parameter by default and expose it only where it is wanted. Disabled means absent from the schema, absent from `describe_tools`, and rejected if supplied anyway. Extends RFD 042, which considered hidden parameters and rejected them. Both of its objections have since been answered by machinery that post-dates it, so the reversal is argued explicitly rather than assumed. Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A tool parameter is either in the JSON schema for every conversation or it does not exist. A parameter that is useful in one context and noise in the rest has nowhere to live: declaring it unconditionally makes every conversation reason about an argument it will rarely use, and moving it to
optionstakes the choice away from the model entirely.The draft adds
enabledto a parameter's configuration, so a config layer can hide a parameter by default and expose it only where it is wanted. Disabled means absent from the schema, absent fromdescribe_tools, and rejected if supplied anyway.Extends RFD 042, which considered hidden parameters and rejected them. Both of its objections have since been answered by machinery that post-dates it, so the reversal is argued explicitly rather than assumed.