fix: add header length constraint to question.txt #8055
+1
−0
Conversation
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
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
pschiel
force-pushed
the
question-tool-description
branch
from
b221113 to
13ed02f
Compare
pschiel
force-pushed
the
question-tool-description
branch
from
13ed02f to
7c5d678
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #7616
Cause: agents sometimes violate the 12-character header limit because JSON Schema constraints like "maxLength": 12 are buried in nested parameter definitions and have lower attention weight compared to prominent natural language instructions in the tool description, causing the LLM occasionally to miss or forget the constraint during generation.
Fix: add it to description text in question.txt