Two tools with clear verb-noun naming (get_current_time, convert_time) and reasonable descriptions (avg 65 chars). Both have Zod schemas with type definitions and parameter descriptions. However, descriptions are below the 194-char baseline and lack context on WHEN to use each tool or what downstream operations they enable. Output schemas are not explicitly documented, helpers.ts defines TimeResult and ConversionResult interfaces, but these are not visible in the tool registration. Error handling returns plain text errors without recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.

• Document output schemas in tool registration. Add a 'returns' field or inline schema comment showing TimeResult structure: {timezone, datetime, date, time, day_of_week, is_dst, utc_offset}.
• Expand tool descriptions to 100-200 chars. Example: 'Get the current date and time in a specified timezone. Returns datetime, date, time, day of week, DST status, and UTC offset. Use this to answer "What time is it in Tokyo?" or to get the current time before calling convert_time.'
• Add tool annotations: set readOnlyHint=true and idempotentHint=true on both tools to signal they are safe to cache and retry.
• Enhance error messages with recovery guidance. Example: 'Invalid timezone "Americ/New_York". Did you mean America/New_York? Use IANA timezone names like America/New_York, Europe/London, Asia/Tokyo.'
• Add a discovery tool or resource listing valid IANA timezones, or document the constraint in convert_time description: 'target_timezone must be a valid IANA timezone (e.g. America/New_York, Europe/London, Asia/Tokyo).'