Server has 35 tools with consistent naming (verb_noun pattern: gorgias_*) and basic descriptions. However, parameter schemas are not visible in the provided source code, only tool names and descriptions are shown. Without access to actual Zod schema definitions or JSON Schema, schema quality cannot be verified. Error handling is present (safeHandler wrapper, sanitiseErrorForLLM), but descriptions are brief (10-50 chars) and lack actionable recovery guidance. No evidence of pagination parameters, output schema documentation, or per-parameter descriptions in the visible code. Access control is implemented (access-control.ts), which is a positive signal for security.

• Expand tool descriptions to 100-200 chars. Include: what the tool does, when to use it vs. similar tools, required inputs, and what it returns. Example: 'Create a new support ticket. Requires customer_id, subject, and message. Returns ticket_id for use in follow-up calls. Use gorgias_search_tickets to find existing tickets first.'
• Document input schemas explicitly in source code or README. For each tool, list parameter names, types (string|number|boolean|enum), required vs. optional, constraints (min/max, regex, enum values), and per-parameter descriptions.
• Add pagination to all list tools: accept limit (1-100, default 20) and offset/cursor parameters. Return total_count or next_cursor in response. Document in tool description: 'Returns up to 20 results per page. Use offset to fetch additional pages.'
• Document output schemas for all tools. Specify which fields are returned, their types, and which are safe to chain to downstream tools. Example: 'Returns {ticket_id, customer_id, subject, status, created_at}. Use ticket_id with gorgias_create_message.'
• Enhance error messages with recovery guidance. Instead of 'An internal error occurred', return: 'Failed to create ticket: invalid customer_id. Call gorgias_list_customers to find valid IDs.' Categorize errors as retryable, user-fixable, or fatal.