Server has 7 tools with basic verb-noun naming (get_*, create_*, list_*, perform_*). All tools have descriptions (10-100 chars), but most are minimal and lack context on WHEN to use them or WHAT they return. Input schemas are present with type declarations (string, optional string) and parameter descriptions, but output schemas are completely undocumented, LLMs cannot plan downstream calls. The perform_dr_switch tool has NO input schema visible and a one-line description, violating critical schema and description rules. Error handling is minimal: tools return {'error': '...'} dicts but provide no recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, IRREVERSIBLE). Composition is reasonable, tools are single-purpose, but missing chaining IDs in responses (e.g., create_msk_custom_domain should return zone_id, cluster_arn for follow-up calls). No pagination support despite tools that list resources.

• Add output schema documentation to every tool. Example: 'Returns: {"cluster_arn": string, "cluster_info": {...}, "status": string}'. This enables LLMs to plan chaining.
• Annotate tools with readOnlyHint, destructiveHint, idempotentHint in the tool definition. Map risk levels (READ_ONLY → readOnlyHint=true; WRITE → destructiveHint=true; IRREVERSIBLE → destructiveHint=true, idempotentHint=false).
• Enhance error messages with recovery guidance. E.g., 'Cluster "my-cluster" not found in region us-east-1. Try: (1) verify cluster name, (2) check region, (3) call list_clusters() to see available clusters.'
• Add pagination to list_route53_resource_record_sets: accept limit (default 20, max 100) and next_token parameters. Return total_count and next_token in response.
• Expand perform_dr_switch description to explain prerequisites, parameters (region, cluster_name, target_cluster?), and what happens (e.g., 'Switches traffic from primary to standby cluster. IRREVERSIBLE. Requires confirmation.'). Add input schema with required fields.