The MES Workflow MCP server provides 18 tools with basic schemas and descriptions, but falls short of production quality standards. While tool naming follows verb_noun conventions (get_, list_, search_, record_, generate_, export_, validate_), descriptions are minimal (averaging ~80-100 chars, well below the 194-char baseline) and lack the actionability required for LLM-optimal tool selection. Input schemas are present and properly typed, but parameter descriptions are sparse or generic. Output schemas are completely undocumented, the server provides no guidance on what fields agents should expect from responses, making downstream tool chaining and data extraction error-prone. Error handling is absent; there are no recovery guides, categorization of errors as retryable vs fatal, or actionable error messages. The tools appear well-designed for domain logic (workflow stages, decisions, task dependencies), but the interface is not optimized for LLM interaction.

• Add comprehensive output schema documentation to every tool. For each tool, specify the return type (object, array, or primitive), list all fields with types and descriptions, and include 1 - 2 example responses. Example: get_workflow_overview returns {workflow_id: string, task_count: number, decision_count: number, stages: string[], ...}.
• Expand tool descriptions to 100 - 200 characters with WHEN-to-use context. Pattern: 'Use this to [action]. Call this INSTEAD OF [alternative tool] when [condition]. Returns [key fields]. E.g.: get_stage_details: Use this to retrieve all tasks in a workflow stage. Call this instead of list_all_tasks when you only need one stage. Returns task list, stage metadata, and decision dependencies.'
• Add parameter descriptions that specify format, valid ranges, and constraints. Example: client_name should become 'Client name (alphanumeric, underscores, hyphens; 1 - 50 chars; case-sensitive). E.g., "acme_corp_2024".'
• Implement pagination for list_all_tasks and list_all_decisions. Add limit (default 20, max 100) and offset/cursor parameters. Document in tool description: 'Returns max 20 tasks per call. Use offset/cursor for pagination. Total count included in response.'
• Add structured error handling: Catch common failures (client not found, invalid decision ID, missing workflow), categorize each as retryable|user-fixable|fatal, and return actionable guidance. Example: '{error: "client_not_found", client_name: "xyz", category: "user-fixable", suggestion: "Call list_client_decisions to see available clients."}' instead of a bare 404.