35 tools with consistent naming (verb_noun pattern) and basic schemas. All tools have descriptions (10-200 chars, mostly adequate). Input schemas present for all tools with proper type definitions. However, parameter descriptions are MISSING, the code shows only type definitions, no explanatory text for what each parameter controls. Output schemas are undocumented. Error handling and recovery guidance absent. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Parameter constraints (enums, ranges, formats) are minimal. This is a functional but under-documented toolkit typical of community servers.

• Add parameter descriptions to all tools. For each param, explain what it controls, valid range/format, and dependencies. E.g., 'bandwidthGb: Prepaid bandwidth in GB (1-10000). Raises the hard cap for the zone.'
• Document output schemas for all tools. Define what fields are returned, their types, and which are safe to chain to downstream tools. E.g., cdn_create_zone returns {zone_id: number, hostname: string, upload_token: string}.
• Add tool annotations: mark destructive tools (cdn_delete_zone, vps_reinstall, build_delete_trigger) with destructiveHint=true; mark read-only tools with readOnlyHint=true. This enables LLM safety guardrails.
• Implement error handling with recovery guidance. Return structured errors like {error: 'invalid_region', message: 'Region must be one of: us-east, us-west, eu-central', suggestion: 'Call cdn_catalog to see available regions'}.
• Add parameter constraints: enumerate valid regions, OS templates, and provider values; specify numeric ranges (bandwidthGb 1-10000, cpu_cores 1-64); mark mutually exclusive params (e.g., productCode vs explicit bandwidth/storage).