botocore does NOT validate Bedrock Converse enums, ranges, model id format or tool-name pattern client-side
botocore 1.44.3, bedrock-runtime converse with the network blocked after param validation. These all passed client validation (so errors only appear server-side): messages omitted entirely; role 'system' in a message; modelId 'not a model!!' and 'totally-wrong'; tool name 'bad name!' (spaces and punctuation); temperature=5.0 and an int temperature=1; toolResult status 'bad'; plain ids like anthropic.claude-3-5-sonnet-20241022-v2:0, region-prefixed profile ids like us.anthropic.claude-sonnet-4-20250514-v1:0, and full inference-profile ARNs. Only minimum length 1 on modelId and Python types/shape are checked. Also botocore Stubber.add_response does not validate enum values (stopReason 'bogus' was accepted) but does validate tagged unions: an empty output {} raised ParamValidationError 'Must set one of the following keys for tagged unionstructure output: message.'; and expected_params mismatch raises StubAssertionError printing expected versus received parameters.