Server has 5 tools with complete input schemas and descriptions, but quality is inconsistent. Tool names lack clear action verbs (e.g., 'query_visitor_info' is vague). Descriptions are present but brief (avg ~50 chars, below 194-char baseline). No output schemas documented. Parameters lack depth, many missing format constraints, ranges, or validation guidance. Error handling returns generic text responses without recovery guidance. No tool annotations (readOnlyHint/destructiveHint). mysql_query exposes dangerous SQL execution without clear safeguards or parameterization warnings.

• Add output schemas to all tools. Document the structure of weather data, repo list, repo details, query results, and visitor info. Use JSON Schema with typed fields and descriptions.
• Rename 'query_visitor_info' to 'get_visitor_appointments' or 'search_visitor_bookings' to clarify the action and resource. Rename 'github_get_repo_info' to 'get_github_repo_details' for consistency.
• Expand mysql_query description to emphasize parameterization: 'Execute parameterized SQL queries. ALWAYS use the params array to prevent SQL injection. Never embed user input directly in the query string.'
• Add tool annotations: mark mysql_query with destructiveHint=true; mark all github and weather tools with readOnlyHint=true. This signals safety properties to LLMs.
• Enhance error messages with recovery guidance. E.g., 'Weather API timeout. Retry with a simpler location name (e.g., "London" instead of "London, Greater London, UK").' or 'GitHub rate limit exceeded. Wait 60 seconds before retrying.'