Single tool 'network_lookup_dns' has a well-structured schema with proper types and descriptions for both parameters (domain, type). The tool description is comprehensive (280+ chars) and includes use cases, return structure, and explicit guidance on when NOT to use it (anti-patterns). Parameter descriptions are clear and actionable. However, the description embeds example output JSON inline rather than documenting the output schema formally, and lacks explicit error handling guidance. The tool follows verb_noun naming (network_lookup_dns) and accepts constrained enum values for the 'type' parameter. No critical gaps, but output schema documentation could be more formal.

• Add formal output schema to tool definition: document the structure of 'records' array, 'queryTime' type (integer ms), and 'resolver' field.
• Extend description with error guidance: 'Returns error if domain is invalid, unreachable, or record type is unsupported. Retry with a different record type if available.'
• Document result limits: 'Returns up to 100 records per query. For domains with many records, filter by type parameter.'
• Add parameter constraint for 'domain': specify format (FQDN, no wildcards) and length limits (1-253 chars per DNS spec).
• Consider adding optional 'limit' parameter to cap result size and support pagination via cursor or offset.

Inferred effective spec: 2025-06-18+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry