Single tool with clear purpose and good description (194 chars, within baseline 34-392). Input schema present with Zod validation. However, output schema is completely undocumented, LLMs cannot plan downstream operations without knowing return fields. Parameter description is adequate but lacks format/constraint details. Error handling exists but lacks recovery guidance. No tool annotations (readOnlyHint, etc.). Code snippet truncated, preventing full validation of error paths.

• Document the complete output schema in the MCP tool definition. Include all fields from Clearance interface (cf_clearance, user_agent, proxy, expires_at, seconds_until_next, cached, plan, free_calls_remaining) with types and descriptions so LLMs know what to expect.
• Add format constraints to the 'domain' parameter: specify valid TLD patterns, length limits (e.g., 1-253 chars), and clarify that internationalized domains are/are not supported. Replace 'Hostname only, no scheme or path' with a regex pattern or enum of examples.
• Enhance error handling with recovery guidance. Document possible errors (API_KEY not set, rate limit, no challenge, network timeout) and suggest next steps for each. E.g., 'If you see NoChallengeError, the domain is reachable without Cloudflare, no cookie needed.'
• Add readOnlyHint annotation to solve_cloudflare to signal that the tool is safe to retry and does not modify state. This helps agents make better retry decisions.
• Validate RAPTORWAYZ_API_KEY at server startup (in McpServer constructor or initialize handler). Fail with a clear error message before any tool is called, rather than deferring to runtime.