Server defines 7 read-only tools with consistent naming (verb_noun pattern: get_*, search_, list_). All tools have descriptions (avg 95 chars, within baseline 34-392). Input schemas present with type definitions and parameter descriptions. However, output schemas are not documented in the provided code, and descriptions lack actionable context (e.g., when to use get_page vs get_page_by_title, what fields are returned). No error handling guidance visible. Tool composition is sound, each tool has one responsibility, but parameter descriptions could be more specific about constraints and formats.

• Document output schemas for all tools. Specify which fields are returned (e.g., get_page returns {page_id, title, body, created_date, author_id}). Include chaining IDs (page_id, space_key) so agents can compose downstream calls.
• Add enum constraints to 'format' and 'type' parameters in JSON Schema. Replace description examples ('storage' or 'view') with formal enum: ["storage", "view"].
• Add min/max bounds to numeric parameters. E.g., limit: {type: integer, minimum: 1, maximum: 50, description: "Maximum results (1-50, default 10)."}
• Clarify tool selection in descriptions. E.g., get_page: 'Use when you have the numeric page ID.' get_page_by_url: 'Use when you have a full Confluence URL.' get_page_by_title: 'Use when you know the exact title and space key but not the ID.'
• Add error handling guidance. E.g., search_confluence: 'If CQL query is invalid, returns error with suggestion. If no results, returns empty list, try broader search terms.' get_page_by_title: 'If page not found, returns 404, try search_confluence to find the correct title.'

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

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