fix: make FileUploadable s3key description dynamic based on FILE_BACKEND
loading diff…
When FILE_BACKEND=base64 (on-prem), the s3key field description and examples now reflect base64 data URL format instead of S3 keys. This helps LLMs understand they can pass base64 content in the s3key field.
Default (FILE_BACKEND=s3 or unset):
"The S3 key of a publicly accessible file, typically returned from a previous download action that stored the file in S3."
On-prem (FILE_BACKEND=base64):
"The file content as a base64-encoded string or a base64 data URL (e.g. 'data:application/pdf;base64,JVBERi0x...')."
The env var is checked at class definition time (import), before schema push to the registry.
Related: #23235, Slack thread
FILE_BACKEND=base64 shows base64 description🤖 Generated with Claude Code