Two tools with minimal descriptions and incomplete schemas. query_pokemon and battle both lack parameter type definitions in visible code (only string types inferred from FastAPI Query/param hints, not explicit JSON Schema). Descriptions are present but generic (10-50 chars). No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges). Tool names are acceptable but descriptions fail to explain WHEN to use each tool or what they return. Missing idempotency hints, dependency documentation, and recovery guidance.

• Add formal JSON Schema to tool definitions with explicit type, description, and constraints for each parameter. Example: {"name": {"type": "string", "description": "Name of the Pokémon (case-insensitive, e.g. 'pikachu')", "minLength": 1, "maxLength": 50}}
• Expand tool descriptions to 100-200 chars. Example for query_pokemon: 'Retrieve detailed information about a Pokémon by name, including stats, types, abilities, moves, and evolution chain. Returns structured data suitable for comparison or battle simulation.'
• Document output schemas explicitly. Example: 'Returns PokemonInfo object with fields: id (int), name (str), types (list), abilities (list), base_stats (dict), moves (list), evolutions (list), is_fully_evolved (bool).'
• Add error handling guidance to descriptions. Example: 'If Pokémon not found, returns error. Try search_pokemon() with partial name or list_pokemon() to discover valid names.'
• Add parameter descriptions explaining format and constraints. Example for pokemon1/pokemon2 in battle: 'Name of a valid Pokémon (case-insensitive). Must exist in Pokédex. Use query_pokemon() first to verify.'

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

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