Single tool with adequate naming but significant gaps in schema documentation, parameter descriptions, and error handling. The tool name 'dns-query' follows verb-noun convention and is clear. However, the input schema lacks proper parameter type constraints (no enum for DNS record types, no format/pattern validation), output schema is completely undocumented, and error handling is absent. The code contains a TODO comment ('TODO: Validate inputs') indicating incomplete validation. For a tool operating on external DNS infrastructure, the lack of error guidance, timeout handling, and result documentation is problematic.

• Document output schema explicitly. Specify: 'Returns {domain: string, type: string, records: string[]}, where records is an array of resolved values (IPs for A/AAAA, mail servers for MX, etc.)'.
• Replace free-form 'type' parameter with enum constraint in Zod schema: z.enum(['A', 'AAAA', 'MX', 'TXT', 'CNAME', 'NS', 'SOA', 'PTR', 'SRV']).describe('DNS record type. A=IPv4, AAAA=IPv6, MX=mail server, TXT=text record, etc.').
• Implement error handling with try-catch and categorize failures: wrap resolver.resolve() in try-catch; on ENOTFOUND return 'Domain not found: {name}. Check spelling or use describe_dns_zone to list available records.'; on timeout return 'DNS query timed out after 5s. Resolver may be unavailable.'; on EFORMERR return 'Invalid DNS query format for record type {type}. Valid types: A, AAAA, MX, TXT, CNAME, NS, SOA, PTR, SRV.'.
• Add explicit timeout to resolver: const resolver = new dns.Resolver(); resolver.setServers(['8.8.8.8', '8.8.4.4']); resolver.setTimeout(5000); and catch ETIMEOUT separately.
• Enhance parameter descriptions: 'name' → 'The domain name to query (e.g. google.com, api.example.org). For reverse DNS (PTR), use dotted-decimal notation reversed, e.g. 1.2.3.4.in-addr.arpa.'; 'type' → 'DNS record type (A=IPv4 address, AAAA=IPv6 address, MX=mail exchange server, TXT=text record, CNAME=alias, NS=nameserver, SOA=start of authority, PTR=reverse lookup, SRV=service record).'.
• Remove TODO comment and complete input validation. Validate before calling resolver: if (!name || name.trim() === '') return error('Domain name cannot be empty'); if (!['A','AAAA','MX','TXT','CNAME','NS','SOA','PTR','SRV'].includes(type.toUpperCase())) return error(`Invalid record type: ${type}. Must be one of: A, AAAA, MX, TXT, CNAME, NS, SOA, PTR, SRV`).