Thoth exposes 5 read-only tools via HTTP transport with consistent naming (verb_noun pattern: list_, get_). All tools have descriptions (50-150 chars, meeting baseline 34-392 range). However, input schemas are not visible in the provided source code, only tool names and descriptions appear in lib/mcp/tools/index.ts. Without seeing parameter definitions, types, or output schemas, schema quality cannot be verified. Descriptions are adequate but generic (e.g., 'Read-only. Lists every Thoth systematic-literature-review run...' lacks WHEN/WHY context). No error handling guidance visible. All tools are read-only (low risk), but lack of schema visibility and missing parameter documentation are significant gaps.

• Add explicit input schemas to all tools in lib/mcp/tools/index.ts. For list_* tools, include limit (1-100, default 20), offset/cursor, and filter parameters with type definitions and descriptions.
• Document output schemas for each tool. E.g., list_reviews should specify: [{review_id: string, status: enum, critic_score: number, faithfulness_score: number, claim_count: number, citation_count: number}].
• Expand descriptions to 100-150 chars with WHEN/WHY guidance. E.g., 'Lists all SLR runs you own with status and quality scores. Call this first to discover available reviews, then use get_review_draft to fetch full content.'
• Add error handling guidance to descriptions. E.g., 'Returns 404 if review not found or not owned. If 404, call list_reviews to verify the review exists and you have access.'
• For list_* tools, document pagination: 'Returns up to 20 results per page. Use offset parameter to fetch additional pages. Total count included in response.'