Server has 4 tools with clear verb-noun naming and detailed descriptions (avg 180 chars, within baseline 194). All tools have input schemas with type definitions. However, output schemas are not documented in the visible code, parameter descriptions lack constraint details (ranges, enums, formats), and error handling lacks recovery guidance. Tool 4 (lemon_squeezy_webhook) has a complex nested schema that is difficult to parse. No tool annotations (readOnlyHint/destructiveHint) present despite clear risk profiles.

• Document output schemas for all tools. Create explicit response type definitions showing all returned fields, types, and whether they are required. Example: get_package_risk_metrics returns {package_name: string, mci: number, dri: number, asi: number, timestamp: ISO8601, ...}.
• Add enum constraints for package_name ecosystem prefix. Define valid ecosystems (npm, pypi, maven, etc.) as an enum in the parameter schema. Add regex pattern '^[a-z]+/[a-z0-9@._-]+$' to enforce format.
• Enhance error messages with recovery guidance. When RegistryNotFound is raised, return: 'Package "npm/unknown" not found. Try search_packages(query="unknown") to find similar packages.' When timeout occurs, suggest: 'Fetch in progress. Retry in 10 seconds or check status with get_package_risk_metrics(package_name="...").'
• Add tool annotations to schema. Mark get_package_risk_* tools with readOnlyHint=true. Mark lemon_squeezy_webhook with destructiveHint=true and idempotentHint=false (token allocation is not idempotent).
• Flatten and document lemon_squeezy_webhook schema. Replace nested 'meta.event_name' with top-level 'event_name' enum (subscription_created|subscription_payment_success|subscription_updated|subscription_cancelled|subscription_expired). Document required fields: event_name, subscription_id, user_email, variant_id. Add HMAC validation error guidance.