Two tools with minimal descriptions (10-20 chars each) and no parameter descriptions. GetMonkeys has empty input schema ({}); GetMonkey has one parameter with a description. No output schemas documented. No error handling guidance. No tool annotations. Naming is verb-based but descriptions are too terse to guide LLM selection. Lacks pagination, result limits, and structured output documentation.

• Expand GetMonkeys description to 50-100 chars: 'Retrieve a complete list of all known monkey species with location, population, and image data. Use this to discover available monkeys before calling GetMonkey by name.'
• Expand GetMonkey description to 60-100 chars: 'Fetch detailed information for a specific monkey by name (case-insensitive). Returns location, population, coordinates, and image URL. Returns null if not found, try GetMonkeys to see available names.'
• Document output schema for both tools. GetMonkeys should return {monkeys: [{name, location, details, image, population, latitude, longitude}], total_count}. GetMonkey should return {name, location, details, image, population, latitude, longitude} or null.
• Add error handling: if GetMonkey returns null, include guidance: 'Monkey not found. Call GetMonkeys to see available species.' If the HTTP service fails, return a retryable error with timeout guidance.
• Add pagination to GetMonkeys: accept optional limit (default 20, max 100) and offset parameters. Return total_count and next_offset so agents can iterate without fetching all monkeys at once.

Inferred effective spec: <=2025-11-25.

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