homework-mcp has well-structured tool definitions with complete input schemas and clear descriptions. All three tools are properly registered with JSON Schema validation. However, output schemas are not documented, parameter descriptions lack depth (e.g., no format constraints or validation rules), and error handling lacks recovery guidance. The tool names follow verb_noun convention (homework_schedule, homework_list, homework_cancel) which is good, but descriptions could be more concise and action-oriented. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite homework_cancel being reversible and homework_list being read-only.

• Add formal output schema declarations to all three tools in the ListToolsRequestSchema response. Document return types as JSON Schema objects with field descriptions.
• Enhance homework_schedule parameter descriptions: add format='date-time' to due_at, specify prompt length constraints (e.g., 'non-empty string, max 10000 chars'), and clarify title is optional with max length.
• Add tool annotations: set readOnlyHint=true on homework_list, destructiveHint=true on homework_cancel (since it modifies state), and idempotentHint=true on homework_schedule (same input = same scheduled task).
• Improve error messages with recovery guidance. E.g., 'Task not found: {id}. Call homework_list to see scheduled tasks.' and 'Cannot cancel task in {status} state. Only scheduled tasks can be cancelled.'
• Document the implicit default behavior of homework_list in the filter parameter description: 'If omitted, defaults to status="scheduled". Use filter.status to inspect other states: firing, fired, cancelled.'