Strong domain-specific tool set with clear, detailed descriptions and well-structured schemas. All 13 tools have descriptions (avg ~150 chars, within baseline 34-392 range). Parameters consistently typed and described. Output schemas documented in descriptions. Main gaps: no tool annotations (readOnlyHint/destructiveHint/idempotentHint), no error recovery guidance in descriptions, and some parameter constraints could be more explicit (e.g., version enum, entity_type enum). Naming is verb-forward and clear (get_*, search_*, read_*). Composition is sound, each tool has one responsibility. No security issues detected (read-only operations, no secrets in params).

• Add readOnlyHint: true to all 13 tool definitions to formally declare they are safe to call without side effects.
• Convert version, entity_type, language, and kind parameters to enum constraints in JSON Schema. Example: 'version': {'type': 'string', 'enum': ['BSB', 'WEB']}.
• Enhance descriptions with recovery guidance. E.g., get_passage: 'If reference format is unclear, try search() with keywords first.' get_entity: 'If entity not found, try entities_in_passage() to discover entities in a known verse.'
• Document output schemas formally in tool definitions (e.g., 'Returns: {results: [{text: string, reference: string, score: number}], total: number}').
• Add idempotentHint: true to all tools to signal they can be safely retried without duplicate side effects.