morse is a minimal STDIO-only MCP server with 2 simple tools (encode, decode). Both tools have basic descriptions and input schemas with required parameters. However, descriptions are terse (under 100 chars), parameter descriptions are completely absent, output schemas are undocumented, and error handling is minimal. The tools follow a clear verb_noun pattern (encode/decode) but lack the depth expected for production use. No tool annotations, no pagination, no recovery guidance in errors.

• Add parameter descriptions: 'text' should explain 'Plain text to encode (A-Z, 0-9, and common punctuation). Spaces separate words.' 'morse' should explain 'Morse code string with spaces between letters and " / " between words.'
• Expand tool descriptions to 150-250 chars. Include WHEN to use each tool and what format to expect. E.g., 'Encode plain text to International Morse code (ITU-R M.1677-1). Returns letters separated by spaces, words by " / ". Handles A-Z, 0-9, and punctuation.'
• Document output schema in tool descriptions or via a separate schema field. Specify that both tools return a single text field containing the encoded/decoded result.
• Enhance error messages with recovery guidance. Instead of 'morse failed: ...', return 'Invalid morse format: expected spaces between letters and " / " between words. Example: ".... . .-.. .-.. --- / .-- --- .-. .-.. -.."'
• Add tool annotations: set readOnlyHint=true on both tools since they perform no state mutations and are safe to retry.