Two tools with basic schemas and minimal descriptions. Tool names are acceptable but descriptions are extremely terse (6-18 chars vs. baseline 194 chars). No output schema documented. No error handling guidance. Parameters like 'bounds' and 'no_annotations' have no descriptions at all. The 'geocode' tool description is only 16 characters ('Forward geocode.'), below the 20-char floor for meaningful descriptions.

• Expand tool descriptions to 100-200 chars. Example for geocode: 'Forward geocode a location query (address, place name, or coordinates) to get latitude, longitude, and address components. Returns up to 10 results by default. Requires OpenCage API key.'
• Add descriptions to all parameters. Example: 'language: ISO 639-1 language code (e.g. en, fr, de) for results. Defaults to English.' and 'bounds: Bounding box as sw_lon,sw_lat,ne_lon,ne_lat to restrict results to a geographic region.'
• Document output schema in code comments or a separate schema definition. Specify that both tools return an object with 'results' array containing {lat, lon, formatted, components, ...} and 'total_results' count.
• Inject API key from OPENCAGE_API_KEY environment variable by default; only accept _apiKey parameter as override for testing. Remove _apiKey from user-facing tool schema.
• Add error recovery hints: on 429, suggest 'Rate limit reached. Wait before retrying or upgrade to paid tier.' On 401/403, suggest 'Invalid API key. Sign up at https://opencagedata.com/users/sign_up for a free key.'