33 tools with consistent verb_noun naming (ticket_*, user_*, asset_*, etc.). All tools have descriptions (avg ~80 chars, baseline 194). Input schemas present with type definitions and parameter descriptions. However, output schemas are NOT documented, critical gap per pattern:tool. No error handling guidance, no recovery paths, no actionable error messages. Missing tool annotations (readOnlyHint/destructiveHint). Pagination parameters present but inconsistently applied. No enum constraints on IDs (categoryId, priorityId, statusId, etc. are free-form strings). Descriptions are functional but generic, lack WHEN/WHY context and dependency hints.

• Document output schemas for all 33 tools. Include field names, types, and descriptions. Example: ticket_get returns {TicketId: string, Subject: string, Description: string, StatusName: string, CreatedDate: ISO8601, ...}. This enables LLMs to chain calls and extract required fields.
• Add error handling guidance to write tools. Example for ticket_create: 'If categoryId is invalid, call ticket_list_categories() first. If subject is empty, return error: "Subject required (1-255 chars)."' Per pattern:recovery-guide.
• Add tool annotations to all tools. Mark ticket_create, ticket_update, ticket_close with destructiveHint=true. Mark all read tools with readOnlyHint=true. Mark idempotent tools (e.g., ticket_get) with idempotentHint=true. Per current spec (2026-07-28).
• Replace free-form ID parameters with enums or discovery tools. For ticket_create, either: (a) add enum constraints to categoryId/priorityId by calling ticket_list_categories/priorities first, or (b) accept human-readable names (category_name, priority_name) and resolve internally. Per pattern:constrained-input.
• Enrich descriptions with WHEN/WHY context and dependency hints. Example: 'Search for tickets by subject or description. Call this first to find a ticket ID before calling ticket_get(). Returns paginated results (default 20 per page).' Per pattern:tool-description.