Server has 5 tools with mixed quality. All tools have descriptions and basic schemas, but descriptions are inconsistent in quality and depth. Parameter descriptions are present but often minimal. Critical gaps: no output schemas documented, no error handling guidance, no enum constraints for constrained inputs (region, bundle_type, application_id), and missing actionable error messages. Tool naming is clear (verb_noun pattern), but parameter naming lacks type suffixes (e.g., 'region' should be 'region_code'). No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Descriptions average ~80 chars, below the 194-char baseline for A+ tools.

• Add output schemas to all tools. E.g., create_instance should document: {instance_id: string, request_id: string, status: string}. Use JSON Schema in docstrings or FastMCP return type hints.
• Convert constrained parameters to enums. E.g., region: Enum['ap-shanghai', 'ap-nanjing', ...] or reference resources://hai_regions for valid values. Prevents hallucinated region codes.
• Add tool annotations via FastMCP. Decorate remove_instance with @mcp.tool(..., destructiveHint=True) and query_instance_network with readOnlyHint=True to signal safety properties to clients.
• Expand parameter descriptions with format/constraint details. E.g., 'region: region code (e.g., ap-shanghai, ap-nanjing), see resources://hai_regions for full list' and 'instance_id_ls: array of 1-100 instance IDs, all in same region'.
• Add error handling guidance. Wrap API calls with try-catch; return structured errors like {error: 'InvalidRegion', message: 'Region ap-invalid not found. Valid regions: ap-shanghai, ap-nanjing', retryable: false}.