Three tools with basic verb-noun naming (get_*). All have descriptions (10-50 chars, below baseline 194 chars). Input schemas present but minimal: get-ip-location has one string param with description; get-my-location and get-api-usage have empty schemas ({}). Output is unstructured text formatting, not typed objects. No parameter validation, error handling, or recovery guidance. No tool annotations. Descriptions lack WHEN/WHY context and are too terse to guide LLM selection.

• Expand all descriptions to 100-200 characters. Include WHEN to use (e.g., 'Call this to find the geographic location of any IP address'), WHAT it returns (e.g., 'Returns city, country, timezone, coordinates'), and any prerequisites (e.g., 'Requires a valid IPv4 or IPv6 address').
• Add proper input schemas to get-my-location and get-api-usage. Even with no parameters, declare the schema as an empty object with a description: 'No input required. Fetches data for the current request IP.'
• Return structured JSON objects instead of formatted text strings. E.g., get-ip-location should return {ip_address, city, region, country, latitude, longitude, timezone, owner, languages, currency} as typed fields, not a formatted string.
• Add error recovery guidance. E.g., 'Invalid IP address format. Expected IPv4 (e.g., 192.0.2.1) or IPv6 (e.g., 2001:db8::1).' or 'API rate limit exceeded. Retry after 60 seconds.'
• Declare tool annotations in the schema. Add readOnlyHint: true to all three tools to signal they are safe to call without side effects.