Server has 4 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (positive), but most are verbose and lack LLM-optimized structure. Parameter descriptions are present but inconsistent in quality. No error handling guidance, no output schemas documented, no tool annotations. The add_note and get_weather tools lack actionable error messages. Naming is acceptable (verb_noun pattern) but descriptions exceed recommended length (194 char baseline). No pagination, no structured output guidance, no recovery hints.

• Document output schemas for all tools. E.g., add returns {type: integer}, get_weather returns {type: object, properties: {temperature: integer, city: string, condition: string}}.
• Rewrite descriptions to be concise (50-150 chars) and LLM-optimized. Focus on WHAT, WHEN, and RETURN. Example: 'add: Add two integers. Returns their sum.' instead of current verbose form.
• Add error handling with recovery hints. E.g., get_weather: 'If city not found, try a larger city name or check spelling. If API fails, verify WEATHER_API_KEY is set.'
• Add tool annotations via FastMCP (if supported) or schema metadata: mark add_note as destructive, add and read_notes as read-only, add as idempotent.
• Validate city_name parameter in get_weather: reject empty strings, log invalid requests, return 'Invalid city name. City must be 2-50 characters.' instead of generic error.