zorath-env exposes 10 tools via MCP with reasonable naming (verb-noun pattern: check, docs, init, etc.) and descriptions present for all tools. However, critical gaps undermine quality: (1) Tool definitions are inferred from Cargo.toml/main.rs CLI argument parsing, not explicit MCP tool registration code, no visible ToolDefinition structs or schema declarations in the provided source. (2) Input schemas are visible in CLI args but NOT in structured JSON Schema format required by MCP, parameter types are inferred from clap derive macros (Option<String>, Option<bool>) rather than explicit JSON Schema with $schema, properties, required arrays. (3) Output schemas are completely undocumented, no indication what check, docs, scan, etc. return. (4) Descriptions are brief (10-50 chars) and lack LLM-optimized context: 'Validate .env against schema' does not explain WHEN to use it vs scan, or what it returns. (5) No error handling guidance visible, tools do not document recovery paths or error categories. (6) No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels (READ_ONLY vs WRITE). Baseline: 549 production tools average 194-char descriptions; zorath-env averages ~40 chars. Per-tool scores reflect these gaps.

• Add explicit MCP tool registration code (ToolDefinition structs or equivalent) with full JSON Schema input schemas including $schema, properties, required arrays, and type declarations for all 10 tools.
• Document output schemas for all tools. Example: check returns {valid: bool, errors: [{field, message}], warnings: [...]}, docs returns {markdown: string, sections: [...]}, scan returns {secrets: [{type, location, severity}]}.
• Expand tool descriptions to 100-200 chars with WHEN/WHY context. Example: 'Validate .env file against a JSON/YAML schema. Use this to catch missing required vars, type mismatches, and invalid formats. Returns validation errors with line numbers and suggested fixes.'
• Add tool annotations: mark check, docs, scan, doctor, export, diff with readOnlyHint=true; mark init, example, fix with destructiveHint=true (for file writes); mark fix with idempotentHint=true if dry_run is supported.
• Document error handling and recovery paths. Example for check: 'If schema not found, returns error with available schema paths. If .env missing and allow_missing_env=false, returns error suggesting --allow-missing-env flag.'

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

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