12 tools with clear verb-noun naming (search_, list_, get_, create_, update_, add_, download_, upload_). All tools have descriptions (avg 65 chars, baseline 194). Input schemas present with type definitions for all params. However, descriptions are significantly below baseline (65 vs 194 chars), most lack context on WHEN to use, prerequisites, or recovery guidance. Parameter descriptions are minimal (avg 35 chars vs baseline 72). No output schemas documented. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. No tool annotations (readOnlyHint/destructiveHint). Composition is sound: tools are single-responsibility, but no batch variants offered. Missing idempotency guidance for write operations.

• Expand tool descriptions to 100-200 chars. Include: what it does, when to use vs similar tools, what it returns, any prerequisites. E.g. 'Search pages by Confluence Query Language (CQL). Use for complex queries; use list_spaces() to discover space keys first. Returns page_id, title, space_key for chaining to get_page().'
• Document output schemas for all tools. Specify returned fields, types, and which IDs enable chaining. E.g. confluence_search returns {results: [{page_id, title, space_key, ...}], total_count}.
• Add error handling with recovery hints. Catch auth errors (401/403) and suggest 'Check ATLASSIAN_API_TOKEN and ATLASSIAN_EMAIL env vars.' Catch 404 and suggest 'Page not found, try confluence_search() to find the correct page_id.'
• Add tool annotations: mark read-only tools with readOnlyHint=true; mark write tools (create_page, update_page, add_labels, upload_attachment, update_diagram_with_links) with destructiveHint=true.
• Expand parameter descriptions with format/constraint hints. E.g. pageId: 'The numeric page ID (e.g. 12345)'; content: 'Page content in Confluence storage format (XHTML-based markup with <ac:*> tags)'; limit: 'Max results to return (1-100, default 10)'.