docs: Fix Guardrail intro to include output validation #697
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.
Problem:
The original introductory sentence stated that guardrails enable validation for just "user input".
Solution:
This change updates the sentence to clarify that guardrails enable validation of "data flowing through your agent system (such as user input or agent output)".
Why this change?
This provides a more accurate and comprehensive initial understanding of what guardrails are used for, as the documentation later details both Input Guardrails (for user input) and Output Guardrails (for agent output). Aligning the introduction makes the documentation clearer from the start.
Specific Change: