Critical failures across all dimensions. 17 tools with identical anti-patterns: (1) Generic action-string parameters instead of verb-noun naming (e.g., 'document' tool with action='info'|'list'|'open' instead of separate get_document_info, list_documents, open_document tools). (2) Minimal descriptions (10-50 chars) that fail to explain WHEN to use each tool or WHAT it returns. (3) Schemas with only 'action' required; all other params optional and undescribed. (4) No output schemas documented. (5) No error handling guidance. (6) No parameter constraints (enums, ranges, formats). This violates 8+ core patterns from arcade.dev/patterns. The server is essentially a thin wrapper around action strings with no LLM-optimized interface.

• Refactor all 17 tools from action-string dispatch to verb-noun naming. E.g., split 'document' into get_document_info, list_documents, open_document, create_document, save_document, close_document, activate_document, export_document_pdf, insert_document_image, get_document_properties, set_document_properties, health_check_document. Each tool name should start with a verb and convey exactly what happens.
• Expand tool descriptions to 150-250 characters. Include: (1) What the tool does, (2) When to use it vs similar tools, (3) What it returns, (4) Any prerequisites. Example: 'Get document metadata (author, title, subject, page count). Call this first to understand document structure before editing. Returns a JSON object with all properties.'
• Document output schemas for every tool. Define the structure of the response, including field names, types, and what each field represents. This enables LLMs to chain tools and extract required IDs for downstream calls.
• Add parameter descriptions and constraints to all optional params. For each param, state: (1) What it controls, (2) Valid values (enum or range), (3) Format (e.g., ISO 8601 for dates, A1 notation for cells), (4) Dependencies on other params. Example: 'para_index (integer, 1-based): Paragraph number. Required if action is 'paragraph' or 'replace_paragraph_text'.'
• Implement error handling with recovery guidance. Return structured errors with: (1) Error code (e.g., 'DOCUMENT_NOT_FOUND'), (2) Human-readable message, (3) Suggested next step (e.g., 'Try list_documents() to find available files'). Categorize as retryable, user-fixable, or fatal.

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

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