Server has 27 tools with mixed quality. Git tools (git_status, git_diff, git_log) have good schemas and descriptions (50-100 chars, proper JSON Schema). However, 16 tools (read_file, write_file, list_directory, analyze_code, refactor_code, etc.) lack visible input schemas and descriptions in the provided source. Only 3 git tools are fully documented in the sample code. Many tools are inferred to exist but not explicitly defined in the source excerpt. Per the rubric, tools without visible schemas score 0 on schema; tools without descriptions score 0-20. This drives the average down significantly. Error handling is present in git tools but absent or unclear for most others.

• Add explicit input schemas and descriptions to all 24 undocumented tools. Use Zod (already a dependency) to define and validate schemas, then export them as JSON Schema for MCP registration. Example: read_file should have {path: string, encoding?: 'utf-8'|'base64'} with descriptions.
• Add tool annotations to all tool definitions: readOnlyHint=true for git_* and all read-only tools; destructiveHint=true for write_file and refactor_code; idempotentHint=true for idempotent operations. This enables MCP clients to warn users before executing dangerous tools.
• Implement confirmation pattern for destructive tools (write_file, refactor_code, run_command, workflow_abort). Return {result: 'input_required', input_schema: {confirm: boolean}} to require explicit user confirmation before executing.
• Add pagination to git_diff: accept offset/limit parameters and return {diff: string, total_lines: number, truncated: boolean, next_offset?: number}. This allows agents to retrieve large diffs incrementally.
• Enhance error messages with recovery guidance. Example: 'File not found at /path/to/file. Use list_directory("/path/to") to see available files.' This matches pattern:recovery-guide and helps agents self-correct.

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

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