Five read-only tools with complete input schemas and descriptions. Naming is clear and verb-based (sjbrowse, sjrecall, sjread, sjtable, sjfind). Descriptions are detailed (100-200 chars) and explain purpose well. All parameters have types and descriptions. However, output schemas are not documented in the source, only input schemas are visible. No error handling guidance, no recovery patterns, and no tool annotations (readOnlyHint missing despite all being read-only). Parameter descriptions lack format constraints (e.g., date format stated but not enforced via pattern). No pagination metadata (total count, next_cursor) documented for list-returning tools.

• Add output schema documentation for each tool. Example for sjbrowse: 'Returns {artifacts: [{type, host, project, date, topic, sid, path, size, turns}], total: int, offset: int}'.
• Add readOnlyHint: true annotation to all five tools in the MCP tool definition to signal safety to agents.
• Document pagination response fields: add 'total' (total matching artifacts) and 'has_more' (boolean) to sjbrowse and sjtable responses.
• Add JSON Schema pattern constraints: date parameters should use pattern: '^\d{4}-\d{2}-\d{2}$' to enforce YYYY-MM-DD format.
• Add error handling guidance to descriptions: 'Returns empty results if no artifacts match filters. If path is invalid, returns error with available paths.' for sjread.