Two tools with basic verb-noun naming (lookup_ip, lookup_domain) and adequate descriptions (50-60 chars each). Both have input schemas with typed parameters and descriptions. However, output schemas are completely undocumented, tools return 'Any' with no guidance on structure. Error handling is minimal (generic exception strings). No parameter constraints (enums, ranges), no pagination support, and no guidance on when to use one tool vs. the other. Descriptions lack context on prerequisites, return structure, or when to call each tool. This is a minimal, functional implementation but falls short of production quality.

• Document output schemas explicitly. Define the structure of WHOIS responses (e.g., 'Returns a dict with keys: asn, asn_cidr, asn_country_code, asn_date, asn_registry, nets (list of dicts with name, country, state, city, address, postal_code, abuse_emails)' for IP; similar for domain).
• Enhance error messages with recovery guidance. Instead of 'Error performing IP WHOIS lookup: {str(e)}', return structured errors like '{"error": "Invalid IP address", "hint": "Ensure the IP is in dotted-decimal notation (e.g., 8.8.8.8)", "retryable": false}'.
• Expand tool descriptions to 100-150 chars explaining WHEN to use each tool and what data is returned. E.g., 'Retrieve WHOIS registration data for an IP address, including ASN, network range, country, and abuse contacts. Use this to identify IP ownership and network details.'
• Add input validation with clear error messages. Validate IP format (regex or ipaddress module) and domain format (basic TLD check). Return actionable errors like 'Invalid IP: must be in dotted-decimal notation (e.g., 8.8.8.8)'.
• Document response structure and add result limits. Cap WHOIS responses to essential fields (name, country, abuse_email, asn for IPs; registrar, registrant, admin_contact for domains) to reduce token waste and improve clarity.