Single tool 'atlassian_login' has moderate naming (verb-noun form is present but generic for an auth action) and a reasonable description, but lacks critical schema detail and parameter descriptions. The input schema is visible in the provided source and shows an enum constraint for 'target' and a string 'url' parameter, but parameter descriptions are minimal. There is NO documented output schema, making it impossible for LLMs to know what the tool returns. The tool performs authentication (a stateful, write-level operation) but does not declare error recovery guidance, dry-run support, or clear failure modes. Since this is the only tool and exhibits significant gaps in schema documentation and output specification, the overall definition quality is poor.

• Document the complete output schema: What does atlassian_login return on success? (e.g., { authenticated: bool, service: string, username: string?, expires_at: ISO8601string?, error?: string }). Without this, LLMs cannot chain to downstream tools or validate the login succeeded.
• Add parameter descriptions: 'url' → 'Optional. Override the default service URL (from JIRA_URL or CONFLUENCE_URL env var). Must be an HTTPS URL pointing to the target Jira or Confluence instance.'
• Expand tool description to 50-150 chars covering: WHAT (authenticates via browser-based SSO), WHEN (call before any Jira/Confluence API tools), OUTCOME (stores session cookies; subsequent calls use cached session), and HOW ERRORS RESOLVE (e.g., 'If login times out, call this tool again after manually signing in via atlassian-cli').
• Add error classification to description: 'On failure, returns { authenticated: false, error: <reason> }. Common errors: timeout (retry), cancelled (user canceled browser login), network_error (retryable), invalid_url (check URL format). Each error is retryable except cancelled.'
• Clarify idempotency: 'Calling this tool multiple times with the same target is safe, it refreshes the session if expired or returns the existing cached session if valid. No side effects on repeated invocations.'
• Explain the out-of-band authentication pattern: 'This tool does NOT open a browser in the server process. Instead, it expects the user to have authenticated out-of-band using `atlassian-cli login <target>`. This tool validates and refreshes cached credentials. If AuthRequiredError is raised, guide the user to run `atlassian-cli login <service>` in a terminal first.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry