9 tools with complete schemas and descriptions, but quality is uneven. All tools have verb-noun naming (search_, get_, find_, generate_, explain_, compare_, faith_, etc.) and descriptions (avg 120 chars). Schemas present for all tools with proper types and required fields. However, descriptions lack LLM-optimization guidance (e.g., 'when to use this vs similar tools'), parameter descriptions are minimal, and no output schemas are documented. Error handling and recovery guidance absent. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all being read-only operations. Missing actionable error messages and parameter constraints (e.g., 'limit' has no min/max bounds).

• Add output schemas to all 9 tools. Document the structure of returned objects (e.g., search_scripture returns [{verse_reference, text, translation, relevance_score}], get_verse_analysis returns {verse, analysis, cross_references, original_language_insights}). This enables agents to chain tools and extract data reliably.
• Add readOnlyHint: true to all tool definitions in mcp.json. This signals to agents that these tools are safe to retry and do not modify state, enabling optimized retry strategies.
• Add min/max constraints to numeric parameters. E.g., 'limit' in search_scripture: min=1, max=100, default=20. Document in parameter description: 'Maximum number of results (1-100, default 20).'
• Expand parameter descriptions to 60-100 chars with actionable guidance. E.g., 'translation' → 'Preferred Bible translation (WEB, KJV, ASV, ESV). If unavailable, defaults to WEB. Public-domain texts: WEB, KJV, ASV.'
• Add error handling guidance to tool descriptions. E.g., search_scripture: 'Returns empty array if no matches found. If translation is unsupported, returns error with available translations.' Include recovery hints like 'Try search_scripture with broader keywords' or 'Call get_historical_context for background.'