timecalc provides 11 well-named temporal calculation tools with consistent descriptions and basic parameter documentation. All tools follow verb_noun naming (add, subtract, compare, round, etc.) and descriptions are present (avg ~80 chars). However, parameter schemas lack formal type constraints (enums, ranges, patterns), output schemas are not documented, and error handling guidance is absent. No tool annotations (readOnlyHint, destructiveHint) despite all being read-only. Parameter descriptions are minimal (10-30 chars) and do not explain valid values, formats, or constraints. The server is functional but falls short of production-grade LLM-optimized tooling.

• Add enum constraints to string parameters: overflow ∈ {reject, constrain, balance}, rounding-mode ∈ {ceil, floor, round, trunc}, largest-unit/smallest-unit ∈ {year, month, week, day, hour, minute, second, millisecond}. Use JSON Schema enum field.
• Document output schemas for all tools. E.g., 'add returns {value: string (ISO 8601 temporal), type: "date"|"instant"|"zoned-date-time"}'. Include format and timezone info.
• Add readOnlyHint: true to all tool definitions in the MCP server registration. This signals to agents that these tools are safe to call without side effects.
• Expand parameter descriptions to 50-150 chars. Example: 'The duration to add (ISO 8601 format, e.g., P1Y2M3DT4H5M6S). Negative durations subtract.' Include format hints and examples of valid input.
• Add error handling section to tool descriptions: 'Errors: invalid-date-format (date string not ISO 8601), unsupported-timezone (timezone not recognized), overflow-error (result exceeds valid range). Retry with adjusted parameters or use overflow parameter to handle edge cases.'