Both tools have minimal descriptions (under 80 chars) and empty input schemas with no parameter documentation. Tool names lack action verbs (ipv4, ipv6 are nouns, not verb_noun patterns). No output schema is documented. Error handling is basic (generic Error throws). The server exports a non-standard McpToolExport interface rather than using MCP's standard tool registration. No parameter descriptions, no input validation guidance, no recovery hints.

• Rename tools to verb_noun pattern: 'get_ipv4' and 'get_ipv6'. This signals to LLMs that these are read-only retrieval operations.
• Expand descriptions to 100 - 200 chars. Example: 'Retrieve the caller's public IPv4 address (gateway egress IP). Returns {ip: string}. Use this to identify the client's external IP for logging, geolocation, or network diagnostics.'
• Add explicit output schema documentation. Declare that both tools return {ip: string} with the IP address as a string.
• Implement proper MCP tool registration using the standard protocol format (tools list with name, description, inputSchema) instead of the custom McpToolExport interface.
• Add error handling guidance. Document that network errors (e.g., ipify API down) should be retried, and include a recovery hint: 'If ipify is unavailable, consider caching the last known IP or falling back to a secondary service.'