This is a template repository with 8 basic tools across multiple template examples. All tools have descriptions and input schemas with proper types and parameter descriptions. However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool or what happens on error. No output schemas are documented. Tools lack error handling guidance, recovery hints, or idempotency markers. The 'get-weather' tool has a suspicious implementation (no actual API call visible) suggesting incomplete code. No tool annotations (readOnlyHint, destructiveHint) despite all being marked READ_ONLY. Naming is adequate but generic (calculate-*, format-*, count-*). This is template-grade code, not production-ready.

• Expand all tool descriptions to 100-200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. Example: 'Add two numbers and return the sum. Use this for arithmetic operations. Returns {result: number}.'
• Document output schemas for all tools. Specify return type (object/array), required fields, and field types. Example: {type: 'object', properties: {result: {type: 'number', description: 'The sum of a and b'}}, required: ['result']}
• Add error handling guidance to descriptions. Example: 'Throws error if divisor is zero, ask user to provide non-zero divisor.'
• Add tool annotations to schema. Mark all read-only tools with readOnlyHint: true. Example: {params: {...}, readOnlyHint: true}
• Implement actual get-weather logic or remove the tool. Current implementation is a stub. If keeping it, call a real weather API (OpenWeatherMap, WeatherAPI) and document rate limits and error cases.