The Atlassian MCP server has moderate definition quality with significant gaps. Tool naming follows verb_noun conventions (get-, create-, update-, delete-, search-, list-) which is good. However, descriptions vary widely in quality: some are adequately detailed (e.g., 'confluence_search' with CQL context), while others are minimal or generic (e.g., 'health' with empty input). Parameter schemas are present and use Zod validation with type annotations, but many parameters lack detailed descriptions explaining constraints, formats, or dependencies. Parameter descriptions average 15-40 characters, well below the 72-character baseline for A+ tools. Output schemas are not explicitly documented, responses are formatted as text blocks in JSON rather than structured typed objects. Error handling is minimal; there's no evidence of recovery guidance, error categorization, or actionable error messages. The 'create-jira-issue' and 'update-jira-issue' tools are marked WIP, indicating incomplete implementation. Overall, this server would be usable but would benefit from richer descriptions, documented output schemas, and better error handling.

• Expand parameter descriptions to 50-150 characters and include constraints, formats, and examples. For example: 'limit' should be 'Maximum number of results per page (1 - 100, default 20)'; 'cql' should be 'Confluence Query Language (CQL) string (e.g., type = page AND space = DOCS). See https://... for syntax.'
• Document output schemas explicitly for each tool. Return structured objects with typed fields instead of concatenated text strings. Example: get-page should return {title: string, url: string, content: string, lastModified: ISO8601string, author: string} not 'Title: X\nURL: Y\n\nContent'.
• Complete or remove WIP tools. create-jira-issue and update-jira-issue should either have full implementation and documentation, or be hidden/removed. Mark completed status in descriptions.
• Implement error recovery guidance. When a resource is not found, return structured errors with suggestions. Example: 'Space "UNKNOWN" not found. Available spaces: [DOCS, ENGINEERING, MARKETING]. Did you mean DOCS?'
• Add a confirmation step for destructive operations. Implement a pattern where delete-page and delete-jira-issue first return a summary of what will be deleted and require an explicit confirmation parameter or separate confirm_delete_* tool.
• Audit all tool responses to ensure no credentials, session tokens, or internal system IDs leak into returned content. Strip metadata irrelevant to chat interactions (pagination internals, audit fields).
• Document pagination fully. For tools returning lists, return a response structure like {results: [...], total_count: N, next_page_token: '...'} and document in tool descriptions that results may be paginated.