/// Validation and formatting policy for tool calls.
///
/// Controls whether tool call validation and error messages use
/// Python-parity behavior (`EggcalcPython`) or strict JSON Schema
/// behavior (`StrictNative`).
///
/// # MCP Boundary
///
/// The MCP server uses `EggcalcPython` to preserve compatibility with
/// Python `eggcalc` clients. This includes Python-style type names in
/// error messages (`NoneType`, `int`, `float`, `str`, `list`, `dict`).
/// JSON booleans are always rejected for numeric parameters in both
/// modes because MCP model-generated booleans for number fields are
/// commonly mistakes.
///
/// # In-Process API
///
/// `ToolRegistry::default()` uses `StrictNative`, which produces
/// standard JSON Schema type names (`null`, `integer`, `number`,
/// `string`, `array`, `object`) and rejects ambiguous inputs.