Server has 6 tools with basic descriptions and no input schemas visible in the source. All tools are READ_ONLY and call external APIs. Descriptions are present but generic (avg ~100 chars, below the 194-char baseline). No parameter descriptions beyond the docstring. No output schemas documented. Error handling returns JSON but lacks recovery guidance. Tools follow a consistent naming pattern (vhc_*) but lack action verbs (get_, list_, verify_). No tool annotations, no pagination support visible, no structured output guidance.

• Add explicit JSON Schema definitions to all tools via FastMCP. Each parameter must have 'type', 'description', and constraints (minLength, pattern, enum) visible in the schema, not just docstrings.
• Rename tools to follow verb_noun pattern: 'verify_isrc', 'search_by_artist_track', 'get_certification', 'list_recent_certifications', 'get_platform_stats', 'get_pricing'. This helps LLMs parse intent from names alone.
• Document output schemas in tool descriptions. E.g., 'Returns {certification_id, artist, track, isrc, status, issued_date}' so LLMs know what fields to extract for downstream calls.
• Enhance error messages with recovery guidance. Instead of 'Connection failed', return 'API unreachable (timeout after 15s). Retry in 30s or check VHC_API_URL environment variable.' This guides agent retry logic.
• Add pagination support to vhc_registry and vhc_stats. Accept 'limit' (1-100, default 20) and 'offset' parameters, return 'total_count' and 'has_more' fields. Large result sets blow context windows.