lore-mcp provides 8 tools with complete input schemas and descriptions. Naming follows verb_noun conventions well (search_lore, get_message_raw, get_thread_summary, etc.). Most parameters are typed and described. However, there are significant gaps: (1) Output schemas are NOT documented, tools return JSON but LLMs cannot predict field structure; (2) Error handling is minimal, no recovery guidance, error classification, or actionable error messages; (3) Many parameter descriptions lack format/constraint details (e.g., 'baseUrl' format=uri is present but others like 'query' in search_lore lack examples of valid syntax); (4) Parameters with complex relationships (e.g., url vs messageId being mutually exclusive via anyOf) are not explained in descriptions; (5) No tool descriptions mention when to use one tool over another (e.g., get_thread_summary vs summarize_thread_llm vs get_thread_mbox). Tool names are clear and domain-appropriate. Most parameter descriptions exist but are terse. Schemas are present and well-formed with proper types, but lack comprehensive field documentation.

• Document return types for all 8 tools. Specify what fields are returned, their types, and whether they are always present. Example: search_lore returns {items: [{message_id: string, subject: string, date: string, from: string, url: string}], total_count?: number}.
• Add error handling to all tools. Return structured errors with a code, message, and actionable recovery hint. Example: {error: 'message_not_found', message: 'Message ID not found', recovery: 'Try search_lore() to find valid message IDs'}.
• Expand parameter descriptions to include format/constraint details. Example: 'query (string, required): public-inbox query syntax; valid prefixes: s: (subject), df: (date), l: (list), from: (sender). Example: "s:rust df:2024-01-01.."'.
• Clarify when to use overlapping tools. Add a line to each: 'Use get_thread_summary for lightweight summaries (<1KB). Use summarize_thread_llm for full-content analysis and LLM-powered insights. Use get_thread_mbox for raw message data.'
• Document mutually exclusive parameters explicitly. In get_message_raw description, add: 'Provide either url or messageId; if both are absent, the tool returns an error. scope is optional when using /r/ URLs, required for messageId lookups.'
• Resolve deprecation of 'list' parameter. Either remove it or add a migration note: '(Deprecated: use scope instead; list will be removed in v2.0.)'
• Add pagination to search_lore and list_scopes. Accept 'offset' and 'limit' parameters, return 'total_count' and 'has_more' in response. Document default limits (e.g., default limit=20, max=100).