Server has 4 tools with basic descriptions and empty input schemas. Tool names follow verb_noun convention (get_*, getting_*), which is positive. However, all tools lack parameter descriptions, even optional parameters like 'framework' and 'char_prefix' have no guidance on valid values, formats, or constraints. Descriptions are present but generic (34 - 72 chars), below the 50 - 200 char LLM-optimized baseline. No output schemas documented. No error handling guidance. Tool definitions appear hardcoded in ModusFromMCP.py with no visible schema registration in the source provided.

• Add parameter descriptions to all tools. For 'framework', specify: 'Optional framework name (e.g., react, angular, vue). Defaults to react. Determines which code examples are returned.' For 'char_prefix', specify: 'Single character (a - z, 0 - 9) to filter icon names. If omitted, returns all icons.'
• Document output schemas for each tool. E.g., 'Returns an object {components: [{name: string, type: "form"|"ui", description: string}], total: number}' so LLMs know what to expect and can chain calls.
• Expand tool descriptions to 100 - 150 chars. Add context: 'Get installation steps and best practices for Modus components. Call this first if you are new to Modus or need setup guidance.'
• Add error handling guidance. E.g., 'If component not found, returns {error: "Component not found", available: [list of similar names]}. Suggest alternatives to the user.'
• Implement pagination for get_list_of_all_modus_components and get_modus_icons_by_char. Add limit and offset parameters, return total count, and cap results at 50 items per call to avoid context window exhaustion.