Add output_schema caveat to response limiting docs

[jlowin]

The new ResponseLimitingMiddleware truncates oversized responses into a single TextContent block — which means if a tool declares an output_schema, the truncated result won't conform to it. This adds a note to the docs so users aren't surprised.

Extends #3072

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request adds a documentation note to the middleware documentation page explaining that truncating responses when a tool defines an output_schema may result in the output being a plain TextContent instead of the expected structured output. The note is positioned adjacent to the Response Limiting behavior documentation and its usage examples, with no changes to code or runtime behavior.

Possibly related PRs

• PR #3072: Introduces ResponseLimitingMiddleware that truncates tool responses, which is directly related to the documented behavior described in this documentation note.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/response-limiting-schema-note

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}