Server has 11 tools with complete input schemas and descriptions. Naming follows verb_noun convention (mssql_*). Descriptions are present but generic (avg 60 chars, below 194-char baseline). Parameters lack detailed constraints and format guidance. No output schemas documented. Error handling exists but lacks recovery guidance. Missing tool annotations (readOnlyHint/destructiveHint). Risk classification visible in metadata but not in descriptions.

• Add output schema documentation to each tool. Document the structure of returned JSON (e.g., mssql_execute_query returns {rows: [{col1: value, ...}], rowCount: number}). This enables LLMs to plan downstream tool calls.
• Expand tool descriptions to 100-200 chars. Include WHEN to use (vs similar tools), WHAT it returns, and any prerequisites. E.g., 'Get table columns metadata from SQL Server. Call this after mssql_list_connections to explore schema structure. Returns: {tableName, schema, columns: [{name, type, nullable, ...}]}'.
• Add tool annotations via MCP SDK. Expose readOnlyHint for metadata/query tools, destructiveHint for mssql_remove_connection, and idempotentHint for mssql_initialize_connection. This guides LLM retry logic.
• Enhance parameter descriptions with format constraints. E.g., connectionString: 'SQL Server connection string (format: Server=<host>;Database=<db>;User Id=<user>;Password=<pwd>)'. Add minLength/maxLength/pattern to schema where applicable.
• Improve error messages with recovery guidance. Instead of 'Error: Connection failed', return 'Connection failed: <reason>. Try mssql_test_connection first to verify credentials, or call mssql_list_connections to see available connections.'