docs(prompt): tighten shell tool usage guidance wording#2737
Merged
tusharmath merged 2 commits intomainfrom Mar 30, 2026
Merged
docs(prompt): tighten shell tool usage guidance wording#2737tusharmath merged 2 commits intomainfrom
tusharmath merged 2 commits intomainfrom
Conversation
ce7f9c8 to
f57ae40
Compare
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.
Summary
Tighten the wording in the shell tool's usage guidance to use clearer, more directive language that better communicates intent to the model.
Context
The shell tool description contained slightly ambiguous phrasing in two guidance notes. "You do NOT need to use" implies it's optional, while the actual intent is a firm prohibition. Similarly, "Avoid using" is weaker than the intended directive. Stronger, unambiguous language reduces the chance the model will fall back to shell-based file operations when dedicated tools should be used instead.
Changes
head,tail, or other truncation commands" → "you should NOT use" to make the prohibition explicitshellwithfind,grep,cat..." → "Do not use" for consistent, directive tone across all guidance notesTesting
Snapshot tests updated to reflect the new wording in the rendered tool descriptions.
cargo insta test --accept