This server has critical definition quality gaps. All 8 tools have trivial descriptions (e.g., 'GreetPerson description') that provide zero actionable context for LLM tool selection. Parameter descriptions are generic placeholders ('Parameter FirstName') with no guidance on format, constraints, or purpose. While input schemas are present with proper types (string, number, boolean, array), they lack semantic richness. No output schemas are documented. Tool names lack action verbs (GreetPerson, CalculateSum, CheckStatus are noun-based or vague). No error handling guidance, no parameter constraints (enums, ranges), no idempotency hints. This is a code-generated stub that needs significant enrichment before production use.

• Replace all tool descriptions with 50 - 200 character explanations. Example: 'GreetPerson' → 'Greet a person by their first and last name. Returns a personalized greeting message. Use this to generate friendly introductions.'
• Replace all parameter descriptions with actionable guidance. Example: 'Parameter FirstName' → 'First name of the person (1 - 50 characters, letters and hyphens only). Required.'
• Rename tools to verb_noun pattern: 'GreetPerson' → 'greet_person', 'CalculateSum' → 'calculate_sum', 'Tool1' → 'create_user' (or appropriate action). Avoid generic names.
• Document output schemas for each tool. Specify which fields are returned, their types, and what they represent. Example: GreetPerson returns {greeting: string, timestamp: ISO8601}.
• Add error handling guidance to tool descriptions. Example: 'If the name is invalid, returns error 'invalid_name' with suggestion to use letters and hyphens only. Retry with corrected input.'