NestCalcMCP defines 5 simple arithmetic tools with basic Zod schemas and descriptions. All tools have names, descriptions, and input schemas present. However, descriptions are minimal (10-50 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and do not explain output structure. Parameters are typed (number, array) but descriptions are generic ('First number for the operation'). No output schemas documented. Error handling exists (division by zero, empty array) but lacks recovery guidance. Tools follow verb_noun naming (calculate, subtract, multiply, divide, calculateStats) which is good, but descriptions do not differentiate tools or guide LLM selection. Overall: functional but below production quality.

• Expand tool descriptions to 100-200 chars. Example for 'calculate': 'Add two numbers together and return the sum. Use this for basic arithmetic addition. Returns a single numeric result as a string.'
• Document output schemas explicitly. Define that all tools return {content: [{type: 'text', text: string}]} and specify the format of the result string (e.g., 'Result: <number>').
• Add actionable error messages with recovery hints. E.g., 'Error: Division by zero. Provide a non-zero divisor (b parameter) and retry.' and 'Error: Empty array. Provide at least one number in the numbers array.'
• Enhance parameter descriptions with constraints and examples. E.g., 'First number for the operation (any real number, including negative and decimal values)' instead of generic text.
• Add tool annotations to the schema. Mark all tools with readOnlyHint: true and idempotentHint: true to signal to clients that these are safe, repeatable operations.