The server registers 5 tools with basic schemas and descriptions. All tools have names, descriptions, and input schemas visible in handlers.go. However, critical gaps exist: (1) No output schemas are documented anywhere, LLMs cannot know what fields to expect from results. (2) Parameter descriptions are minimal and lack constraints, ranges, or format guidance. (3) No error handling guidance is present. (4) Tool descriptions are generic and do not explain WHEN to use each tool vs. alternatives. (5) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being READ_ONLY. The naming is verb-forward (list_, query_, analyze_, streaming_), which is good, but the descriptions and schemas lack the depth needed to guide LLM tool selection reliably.

• Document the output schema for each tool. Specify what fields (table_name, row_count, schema_details) list_tables returns. Specify what query_albums returns (album_id, title, era, release_date, etc.). Use this pattern: '...returns an object with fields: {album_id (string), title (string), era (enum: Pop|Country|Indie Folk|etc), ...}'
• Convert example values in parameter descriptions to formal constraints. Replace 'era (e.g., Pop, Country, Indie Folk)' with an enum schema: {'type': 'string', 'enum': ['Pop', 'Country', 'Indie Folk', 'Folk']} and update description to 'The album era. Must be one of: Pop, Country, Indie Folk, Folk.'
• Add range constraints to numeric parameters. For min_streams, specify the range (e.g., 0 - 10000 in millions) and explain the unit in the schema constraint description, not just the parameter description.
• Add readOnlyHint: true to all tool definitions in handlers.go. Update ListTools() to include 'readOnlyHint': true in each tool's map.
• Expand tool descriptions to explain prerequisites and when to use each tool. E.g., 'Use this to list all tables in the database BEFORE running queries. Returns table metadata needed for query construction.' For query_albums and query_songs, clarify the difference: 'Use query_albums to filter by era or release info. Use query_songs for streaming/chart data, optionally filtered by album_id.'
• Add error handling guidance in the tool implementation. When a query fails, return a structured error with recovery suggestions, e.g., 'Album not found. Call list_tables() to see available tables, or query_albums() with no filters to discover era values.'

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

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