Single tool with adequate naming (verb_noun pattern) but critical gaps in parameter descriptions and output schema documentation. The ssl_cert_info tool has a clear, actionable description (67 chars), but the input parameter 'hostname' lacks a description entirely, violating the requirement that every parameter must explain what it controls. Output schema is undocumented; the tool returns a dict with 'info' or 'error' keys, but this structure is not formally declared. Error handling returns raw exception strings without recovery guidance. No input validation, no enum constraints, no pagination (not applicable here but relevant for composition patterns). The dynamic tool loading mechanism in main.py obscures explicit tool registration, making it difficult to verify schema completeness.

• Add a description to the 'hostname' parameter: 'The hostname or domain name to retrieve SSL certificate information for (e.g., example.com, api.example.org). Must be reachable on port 443.'
• Document the output schema in the tool docstring: 'Returns a dict with either {"info": str} on success or {"error": str} on failure. The info field contains formatted certificate details (issuer, dates, SANs, days remaining).'
• Enhance error handling to categorize failures and provide recovery guidance. Example: 'Hostname not reachable on port 443. Verify the domain is correct and the server is online. Retryable: yes.' vs 'Invalid hostname format. Must be a valid domain name (e.g., example.com).'
• Add input validation: check hostname length (max 253 chars), reject obviously invalid formats (spaces, special chars), and validate before attempting socket connection.
• Use explicit tool registration with @mcp.tool() decorator and inline schema definition instead of dynamic loading, to make parameter types and descriptions visible in the tool definition.