Two tools with minimal definitions. Both lack parameter descriptions entirely, get_courses has empty input schema {}, get_course has one parameter 'title' with no description. Tool descriptions are generic and under 100 chars, providing no context for when/why to use them. No output schemas documented. No error handling guidance. Naming follows verb_noun pattern (acceptable), but descriptions fail to explain what data is returned, prerequisites, or use cases. This server does not meet baseline standards for LLM-driven tool selection.

• Add a description to the 'title' parameter in get_course: 'The exact or partial title of the course to retrieve (e.g., "Java Basics", "LLM"). Partial matches are supported.'
• Expand get_courses description to ~150 chars: 'Retrieve all available courses covering Java, JDK 24, LLM, and LangChain. Returns a list of course objects with id, title, url, and duration. Call this first to discover available courses before requesting a specific one.'
• Expand get_course description to ~150 chars: 'Retrieve a single course by title. Returns course details including id, title, description, url, duration, and difficulty level. Use this after calling get_courses to fetch full details of a specific course.'
• Document output schema for both tools. Example: 'Returns an object with fields: id (string), title (string), url (string), duration (integer, minutes), difficulty (enum: beginner|intermediate|advanced).'
• Add error handling guidance: 'If course not found, returns error with available course titles. If service unavailable, retry after 5 seconds.'