Two tools with basic schemas but significant quality gaps. list-courses has empty input schema (correct) but minimal description (28 chars). generate-notes-from-source has comprehensive Zod schema with 13 parameters, all described, but descriptions are generic and lack actionable guidance. No output schemas documented. No error handling guidance. No tool annotations. Naming is verb-noun compliant but descriptions fall short of LLM-optimization standards (target 50-200 chars; actual ~100-150 chars). Missing recovery guidance and parameter relationship documentation.

• Expand list-courses description to 50-150 chars: 'List all configured courses and their note/transcript storage paths. Call this first to discover available courses before generating notes.'
• Document output schemas: list-courses should return {courses: [{name: string, notesPath: string, transcriptPath: string}]}; generate-notes-from-source should return {notesPath: string, notesFilename: string, transcriptPath?: string, transcriptFilename?: string, status: string}.
• Add parameter relationship documentation to generate-notes-from-source: 'If sourceType is "api", apiMethod and apiHeaders are required. If sourceType is "local-file", sourceLocation is a relative path within the course transcript directory.'
• Add error recovery guidance: 'If course not found, call list-courses to see available courses. If file not found, verify sourceLocation is relative to the course transcript path.'
• Add tool annotations (readOnlyHint for list-courses, destructiveHint for generate-notes-from-source since it writes files) to signal side effects to LLMs.