Server has 4 tools with basic descriptions and tool annotations present, but critical gaps undermine quality. Tool schemas are severely underdocumented: BusinessVerification and BusinessSearch accept complex request objects with only generic 'object' type and no nested field descriptions. Parameters lack type constraints, ranges, enums, or validation guidance. Descriptions are minimal (10-60 chars) and lack WHEN/WHY context. No output schema documentation. Error handling is generic (catch-all exceptions mapped to code 2000). No guidance on parameter dependencies, required fields, or format constraints. Tool annotations (ReadOnly, Destructive, Idempotent) are present but descriptions don't explain consequences or recovery paths.

• Expand BusinessVerification and BusinessSearch descriptions to 100-200 chars explaining: what verification/search does, when to use each, what data is required, and what the response contains. Example: 'Verify a business entity against Trulioo's KYB database. Call after BusinessSearch to confirm identity. Returns verification status, risk flags, and matched entity details.'
• Document the nested schema for BusinessVerifyRequest and BusinessSearchRequest. List required fields (e.g., CompanyName, JurisdictionCountryCode), their types (string, enum, date), formats (ISO 3166-1 alpha-2 for country), and constraints (max length, regex patterns). Use JSON Schema $ref or inline descriptions.
• Add output schema documentation for all tools. For GetCountries, document: 'Returns {CountryISOCodes: string[], Errors: string[]}. CountryISOCodes is a list of ISO 3166-1 alpha-2 country codes (e.g., ["US", "CA", "GB"]). Errors is non-empty only on failure.'
• Implement error classification and recovery guidance. Replace generic 'code 2000' with specific codes (e.g., 4001=invalid_request, 5001=service_unavailable). Include actionable messages: 'Invalid country code. Must be ISO 3166-1 alpha-2 (e.g., US, CA). Call GetCountries to see valid options.'
• Add parameter descriptions for request objects. For BusinessVerifyRequest, document each field: 'CompanyName (required, string, max 255 chars): Legal name of the business entity. JurisdictionCountryCode (required, enum): ISO 3166-1 alpha-2 country code where business is registered.'

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry