Server has 4 tools with basic descriptions and partial schemas. All tools have descriptions (10-100 chars), but parameter schemas lack type information and descriptions. create_checkout has the most complete schema with 4 parameters, but none have descriptions. verify_webhook, get_integrations, and get_settings have minimal or no input schemas. Output is JSON strings, not structured objects. No error handling guidance, no pagination, no idempotent hints. Naming is verb-forward (create_, verify_, get_) but descriptions are terse and lack context on when/why to use each tool.

• Add parameter descriptions to create_checkout: 'amount' (string, e.g. '100.50'), 'currency' (ISO 4217 code, default USD), 'title' (checkout display name), 'external_reference' (merchant's order ID for tracking).
• Add parameter descriptions to verify_webhook: 'raw_body' (raw HTTP request body as string), 'signature_header' (X-Webhook-Signature header value with format t=<timestamp>,v1=<hmac>).
• Return structured objects instead of JSON strings. E.g. create_checkout should return {ok: bool, payment_url: string, transaction_id: int | null, error: string | null} with proper types.
• Expand tool descriptions to 80-150 chars with context: 'Create a U.CASH Pay checkout for crypto/card payments. Returns payment_url and transaction_id. Requires UCASH_CLOUD_TOKEN env var. Call verify_webhook to confirm settlement.'
• Add error recovery guidance: 'If ok=false, check that UCASH_CLOUD_TOKEN is set and amount is a valid decimal string. If verify_webhook returns verified=false, ensure raw_body and signature_header match the exact webhook request.'