ccfolio exposes 5 search and analytics tools for Claude Code conversation history. All tools have descriptions and input schemas with typed parameters. However, there are significant gaps in schema documentation, parameter descriptions lack detail, and output schemas are not formally documented. Tools follow a consistent naming pattern (verb_noun) and are read-only, which is appropriate. The main weakness is that descriptions are text-only and outputs are returned as formatted strings rather than structured JSON, forcing LLMs to parse unstructured text.

• Convert all tool return types from formatted strings to structured JSON objects. For example, search_sessions should return {results: [{session_id, title, date, model, cost, snippet}], total_count, limit_applied} instead of a formatted string. This enables LLMs to extract specific fields and compose with downstream tools.
• Document output schemas formally in tool definitions. Add a 'result' schema showing field names, types, and descriptions. Example: get_session_details should return {session_id: string, title: string, date: string, message_count: int, model: string, estimated_cost_usd: float, tags: string[], files_touched: string[], ...}.
• Add explicit JSON Schema enum constraints for 'sort_by' (list_recent_sessions) and 'period' (get_cost_summary). Replace inline descriptions with formal enum definitions so LLMs know valid options without parsing text.
• Enhance parameter descriptions with constraints, ranges, and examples. For example: 'limit: Max results to return. Range 1 - 100, default 10.' Add format guidance for session_id: 'Full UUID (e.g., 550e8400-e29b-41d4-a716-446655440000), UUID prefix (first 8 chars), or slug (human-readable name, e.g., project-setup-v2).'
• Add pagination support. Include offset and cursor in search_sessions and list_recent_sessions. Return total_count and next_cursor in responses so LLMs can iterate through large result sets without hitting context limits.
• Implement error recovery guidance. When a session is not found, return a structured error like {error: 'session_not_found', message: 'Session not found. Try search_sessions() to find similar conversations.', suggestion: 'search_sessions with partial title or keywords'}. Classify errors as retryable (timeout) vs. user-fixable (invalid input) vs. fatal (permission denied).