Sora exhibits severe definition quality gaps across all 17 tools. Tool names lack clear action verbs (e.g., 'trackPackage', 'researchCountryContext' are vague about intent). Descriptions are present but often cryptic, mixing Japanese and English with technical jargon ('Ranked Local Detection + Bounded Wave Verification') that does not clarify WHEN or WHY to use each tool. Input schemas are visible but lack proper type definitions for complex objects (e.g., 'context' and 'hints' parameters are typed as 'object' with no nested schema). Output schemas are entirely undocumented, no tool declares what fields it returns. Parameter descriptions are minimal (5-15 chars on average) and fail to explain constraints, formats, or dependencies. Error handling is absent from all tool definitions. No tool declares idempotency, destructiveness, or read-only semantics in the schema itself.

• Document output schema for every tool. Example: trackPackage should declare it returns {status, location, estimatedDelivery, carrier, lastUpdate} with types and descriptions.
• Replace bare 'object' parameters with explicit nested schemas. For 'context' in trackByCarrier, define {signal?: AbortSignal, noCache?: boolean} with proper types.
• Rewrite descriptions in English only, 50-150 chars, answering: What does it do? When use it? What does it return? Example: 'Track a package by carrier code. Returns current location, status, and estimated delivery date.'
• Add error handling guidance to tool descriptions. Example: 'If carrier is unknown, returns error with list of supported carriers. Call trackPackageAuto() to auto-detect.'
• Consolidate the 8 provider factory tools into a single 'createCountryIntelProvider(provider_type)' tool with an enum of provider types, reducing cognitive load and tool count.

Inferred effective spec: <=2025-11-25.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained