CLQ is a test/template fixture server with 3 minimal tools. All tools lack parameter descriptions (critical violation of pattern:tool-description). Tool schemas are present but incomplete: parameters have types but NO descriptions. Descriptions themselves are present but extremely brief (10-34 chars, below the 50-200 char LLM-optimized baseline). No output schemas documented. No error handling guidance. Tools are simple (echo, add, get_weather) but lack the rigor expected of production tools. This is a reference implementation, not a production-grade server.

• Add 50-200 character descriptions to each tool explaining WHAT it does, WHEN to use it, and WHAT it returns. E.g. 'echo: Returns the input string unchanged. Use to verify connectivity or test tool invocation. Returns: {message: string}'.
• Add descriptions to all parameters. For 'message', explain format and length limits. For 'a' and 'b', specify numeric range (e.g., 'Integer or float, range -1e6 to 1e6'). For 'city', replace example with enum or pattern constraint.
• Document output schemas for each tool. Define return types as JSON Schema objects. E.g., echo returns {message: string}, add returns {sum: number}, get_weather returns {temperature: number, condition: string}.
• Add error handling guidance. E.g., 'If city is not found, returns error: "City not found. Try a major city name like London, Paris, or Tokyo."'.
• For get_weather, replace example-based description with a formal constraint: city must be a valid city name (2-100 chars, letters/spaces/hyphens only).