Three tools with basic registration but significant quality gaps. Tool names follow verb_noun pattern (good), but descriptions are minimal (avg 95 chars, well below 194-char baseline). Input schemas are present but lack parameter descriptions entirely, critical violation of pattern:tool-description. No output schemas documented. Error handling is absent from tool definitions. The write_firebird_configs tool performs destructive operations (file writes with backups) but has no dry-run guidance in description, and no confirmation pattern. Security concern: credentials loaded from file path without validation.

• Add full parameter descriptions to all three tools. For calculate_firebird_config: 'server_version (string): Firebird or HQbird version identifier (fb2.5, fb3, fb4, fb5, hq2.5, hq5). Determines optimization rules applied.' Repeat for all 11 parameters.
• Document output schemas for each tool. E.g. calculate_firebird_config returns {firebird_conf: string, databases_conf: string, recommendations: string[], warnings: string[]}. Include this in tool registration via InputSchema/OutputSchema fields.
• Expand tool descriptions to 150 - 250 chars. Example: 'Call the IBSurgeon Configuration Calculator API with server specs (version, cores, RAM, database size) to generate optimized firebird.conf and databases.conf. Requires valid credentials file. Returns configuration content and tuning recommendations.'
• Add confirmation pattern to write_firebird_configs. Enhance description: 'Writes firebird.conf and databases.conf to disk with timestamped backups. DESTRUCTIVE: modifies production files. Use dry_run=true first to preview output paths. Requires write permissions to output_dir.'
• Implement error classification in tool handlers. Return structured errors: {error: string, category: 'retryable'|'user_fixable'|'fatal', hint: string}. E.g. 'Credentials file not found at /path/to/creds. Hint: Pass --credentials flag or set FIREBIRD_CREDS env var.'