Four tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. Tool names follow verb_noun convention (getDailyVerse, generateBooks). Descriptions exist but are generic (10-150 chars, below the 194-char baseline). Input schemas present but lack comprehensive parameter descriptions, most params have minimal guidance. No output schemas documented. Admin tools expose systemToken as a parameter, violating secret-injection pattern. No error recovery guidance. Composition is reasonable (single responsibility per tool), but parameter constraints and validation rules are absent.

• Move systemToken to server-side environment variable injection. Remove it from tool parameters. Authenticate via request headers or context instead.
• Document output schemas for all tools. Specify fields returned (e.g., getDailyVerse returns {date, reference, text, translation}), types, and which fields are safe to chain to other tools.
• Expand parameter descriptions with validation rules and discovery hints. E.g., 'bibleTranslationSlug: Valid translation identifier (e.g., "vdcc", "kjv"). Call list_translations() to discover available slugs.'
• Add error handling guidance to tool descriptions. E.g., 'Returns 404 if date is before Bible publication or after today. Returns 400 if bibleTranslationSlug is invalid, call list_translations() to see available options.'
• Implement permission checks for admin tools. Verify caller has admin role before executing generateBooks/generateAllBooks. Log all admin actions with caller identity and timestamp.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry