The server defines 3 tools with clear names and basic descriptions, but has critical gaps in schema documentation, parameter descriptions, and output structure. Tool names follow verb_noun convention (list_sessions, export_session, export_all_sessions), which is good. However, input schemas are only partially visible in the provided code, the pyproject.toml and main server.py excerpt show tool registration but the full schema definitions are not fully shown. Based on what is visible: all three tools have descriptions (10-144 chars), but parameter descriptions are minimal. The export_session tool accepts a 'session_id' that could be 'ID prefix, or slug' but these format constraints are buried in the description rather than formalized in the schema. No output schemas are documented anywhere. Error handling is minimal, no recovery guidance, no categorization of errors (retryable vs fatal). The code shows basic data access patterns and markdown rendering but lacks production-grade safeguards. STDIO transport is a hard cap of 50 max, but definition quality alone pulls the overall average down further due to missing schema details.

• Document output schemas for all three tools. list_sessions should specify it returns an array of objects with fields {id, title, slug, project, time_created, cost}. export_session and export_all_sessions should document that they return {success: boolean, output_path: string, message: string}.
• Expand parameter descriptions to include format constraints and examples. For session_id, write: 'Session identifier: a UUID (e.g. 550e8400-e29b-41d4-a716-446655440000), a UUID prefix (e.g. 550e8400), or a slug (e.g. project-analysis-2025). Slugs are preferred when available.'
• Add bounds to numeric parameters. For limit, write: 'Maximum number of sessions to return (1 - 100, default 20).'
• Document expected failure modes and recovery steps. E.g., 'If export fails with "database not found", ensure OpenCode is installed and has run at least once. If the output directory is not writable, the tool will return an error, try a different directory or ensure write permissions.'
• Add idempotency note: export_session with the same session_id and output_dir will overwrite the previous file. This matters for agents that retry on ambiguous failures.
• Include tool risk annotations in the tool metadata: export_session and export_all_sessions are write operations and should be marked with destructiveHint=false (they create files but do not delete) and idempotentHint=true (re-exporting produces the same output).