Single tool with empty input schema and minimal description. The clear_cache tool has a 127-character description (within acceptable range) but the input schema is an empty object with no parameters documented. No output schema is documented. The server lacks multiple core tools for a Gradescope integration (fetch courses, assignments, grades, analyze performance). Tool naming follows verb_noun convention but the overall toolkit is incomplete for the domain.

• Define explicit output schema for clear_cache: return object with fields 'message' (string), 'timestamp' (ISO 8601 string), 'entriesCleared' (number). Document in tool registration.
• Implement core Gradescope tools: get_courses (list user's courses), list_assignments (fetch assignments for a course), get_grades (retrieve grades for an assignment), analyze_performance (summarize grade trends). Each tool must have full input schema with parameter descriptions and documented output structure.
• Add destructiveHint annotation to clear_cache tool registration to signal to LLMs that this operation is irreversible.
• Enhance error handling: document that clear_cache always succeeds (idempotent), but add error cases for cache system failures with recovery guidance (e.g., 'Cache system unavailable. Retry in 5 seconds or restart the server.').
• Add parameter descriptions and enums where applicable. For future tools, use enums for status fields (e.g., assignment status: 'submitted', 'graded', 'pending'), and provide min/max constraints for numeric parameters (e.g., limit: 1-100).

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry