All 4 tools have trivial descriptions (10-30 chars) and ZERO input parameters with schemas. Tools are named correctly with verb prefixes (get_*), but lack the depth required for LLM-driven agent selection. No parameter descriptions, no output schemas documented, no error recovery guidance. This server falls into the F/D range: barely functional definitions.

• Expand descriptions to 50-150 characters. Example: 'get-external-ip' → 'Retrieve the public IPv4 address of this machine by querying an external IP service. Returns a single IP string. Use when you need to know how this host appears on the internet.'
• Add input parameters with descriptions and types. Even though these tools take no arguments, explicitly document this: 'inputSchema: { type: "object", properties: {}, required: [] }' and note 'This tool requires no parameters.'
• Document output schema in tool description: 'Returns a single text field containing the IP address (e.g., "203.0.113.42"). Returns error text if the lookup fails.'
• Improve error messages with recovery guidance. Instead of 'Failed to get external IP', return 'Failed to fetch external IP from 4.ipw.cn. This may indicate a network issue or the service is unavailable. Try again in a few seconds, or check your internet connection.'
• Replace hardcoded 'en0' with dynamic interface detection. Iterate through networkInterfaces() and return the first non-internal IPv4/IPv6 address, or return an error listing available interfaces if none found.