Server has 24 tools with complete input schemas and descriptions. Naming follows verb_noun convention (get_, create_, update_, delete_, search_). However, two critical issues: (1) confluence_get_space and confluence_get_space_by_key are duplicates with identical functionality, violating single-responsibility and composition patterns. (2) Descriptions are functional but generic (avg ~80 chars), lacking LLM-optimized guidance on WHEN to use each tool vs alternatives. (3) No output schemas documented, LLMs cannot predict response structure for chaining. (4) Error handling is absent from tool definitions. (5) Parameters lack constraints (enums, ranges, patterns) despite many accepting constrained values (e.g., limit should be 1-100, not unbounded). Pagination is present but not consistently documented.

• Remove confluence_get_space_by_key, it duplicates confluence_get_space. Keep only one canonical tool.
• Document output schemas for all tools. Example: confluence_get_spaces should return {spaces: [{id, key, name, type}], limit, start, size, total}. This enables LLMs to chain calls correctly.
• Enhance descriptions with WHEN-to-use guidance. E.g., 'Use confluence_get_page for small pages (<10KB). For large pages, use confluence_get_page_body_chunk with offset/line ranges to avoid context bloat.'
• Add parameter constraints: limit as integer 1-100 (default 25), start as integer ≥0, spaceKey as string pattern ^[A-Z0-9]+$, pageId as string (non-empty). Document in descriptions.
• Add error handling patterns: confluence_delete_page should document 'Returns error if page not found or user lacks delete permission. No undo available, consider archiving instead.' confluence_update_page should mention optimistic locking (version conflicts).