Akamai MCP server has basic tool definitions but significant quality gaps. All 4 tools have names and descriptions, but descriptions are minimal (10-50 chars, well below the 194-char baseline). Two tools (list_groups, list_contracts, get_group_details) have empty input schemas with no parameters documented. The list_properties tool has two optional parameters with descriptions, but lacks output schema documentation. No error handling guidance, no pagination support despite list operations, and no tool annotations (readOnlyHint, etc.). Parameter descriptions are present but sparse. Overall structure is functional but falls short of production-grade quality.

• Expand tool descriptions to 100-200 chars. Example: 'list_groups' → 'Retrieve all Akamai contract groups accessible under your account. Returns group IDs, names, and parent-child relationships. Use this to discover available groups before filtering properties by group_id.'
• Add output schema documentation for each tool. Specify returned fields (groupId, groupName, parentGroupId, etc.), types, and which fields are safe to pass to downstream tools.
• Add pagination parameters (limit: 1-100, offset: 0+) to list_* tools. Return total_count and next_offset in responses. Cap default limit at 20-50 items per pattern:paginated-result.
• Wrap error responses with actionable guidance. Instead of raw exception, return: '{"error": "Failed to fetch groups", "reason": "Authentication failed", "next_step": "Verify ~/.edgerc credentials and retry"}' per pattern:recovery-guide.
• Clarify get_group_details: does it require a group_id parameter, or return all groups? If it duplicates list_groups, consolidate or document the distinction. Add required parameter if needed.

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

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