Three connection-management tools with complete input schemas and descriptions. login and logout have detailed, actionable descriptions (200+ chars) explaining security patterns (ENV_VAR, op:// vault refs) and timezone/worklog_admins configuration. All parameters are typed and described. However, output schemas are not documented, callers cannot infer return structure. Error handling is minimal; no guidance on recovery (e.g., 'connection not found' should suggest list_connections). Tool composition is sound (one responsibility each), but descriptions lack LLM-optimized brevity and missing examples of valid connection names.

• Document output schemas for all three tools. E.g., login returns {connection: str, url: str, email: str, read_only: bool, timezone: str}. list_connections returns {connections: [{connection: str, url: str, email: str, read_only: bool}], total: int}.
• Enhance error messages with recovery hints. In _get_connection(), catch FileNotFoundError and return: 'Connection "<name>" not found. Available: [list]. Call list_connections() to see all saved connections.'
• Clarify logout consequences in description: 'Permanently removes the saved connection config. Active sessions using this connection will fail on next call. This action cannot be undone.'
• Add examples to login description: 'E.g., connection="prod-jira", url="https://company.atlassian.net", email="[email protected]", token="${ATLASSIAN_TOKEN}"'.
• Document list_connections filter behavior: 'Pass connection name to filter results to one; omit to list all saved connections. Returns empty list if no matches found.'