Enterprise MCP has 9 tools across health monitoring and ServiceNow integration. Naming is generally clear and action-oriented (get_*, create_*, update_*). However, critical gaps exist: descriptions are present but mostly generic (10-50 chars), parameter descriptions are minimal or missing, input schemas lack depth, and output schemas are entirely undocumented. The server shows basic structure but lacks the detail required for confident LLM tool selection and composition. No visible error handling guidance, no pagination support for list tools, and no tool annotations (readOnlyHint/destructiveHint). The update_incident tool is particularly sparse, it accepts only incident_id with no description of what fields can be updated.

• Document output schema for every tool. Specify fields, types, and examples. E.g., get_incidents returns [{id: string, short_description: string, status: 'new'|'in_progress'|'resolved', priority: 1-5, created_at: ISO8601, ...}, total_count: integer]
• Expand tool descriptions to 100-150 characters. For get_cpu_usage, add: 'Returns current CPU usage percentage (0-100) and per-core breakdown. Use to monitor server load or trigger alerts when usage exceeds threshold.'
• Add parameter constraints to create_incident: short_description (required, 1-160 chars), description (optional, max 4000 chars), priority (required, 1-5 where 1=critical, 5=low), category (enum: incident|service_request|inquiry).
• Add pagination to get_incidents and get_change_requests: include offset/limit in input, return total_count and next_offset in output. Support at least 100 items per page.
• Specify what update_incident modifies. Add parameter schema: {incident_id, status?, priority?, assignment?, notes?}. Document which fields are mutable and which are read-only.
• Add tool annotations to destructive/modifying tools: mark create_incident and update_incident with modifyingHint=true; mark get_* tools with readOnlyHint=true.
• Add error handling examples: 'If incident_id not found, returns 404 with message: "Incident ABC12345 not found. Try searching with get_incidents() for similar tickets." If priority invalid, returns 400: "Priority must be 1-5, got 6."'
• Validate and document parameter types in schema. priority should be declared as integer with minimum=1, maximum=5, not just default=3.