RAGClaw Lite exposes 7 tools with basic descriptions and input schemas, but falls short of production quality. Tool names follow verb_noun convention (run_python, list_files, delete_file), which is good. However, descriptions are minimal (10-50 chars), parameter descriptions lack depth, and output schemas are not documented. No error handling guidance, no recovery paths, and no tool annotations (readOnlyHint/destructiveHint). The timezone parameter appears on execution tools but lacks validation constraints. File operation tools (list_files, read_file, write_file, delete_file) have identical 1-param schemas with minimal context. No pagination support on list_files despite potential for large directory listings. Security-critical tools (run_shell, delete_file) lack confirmation/dry-run patterns.

• Expand tool descriptions to 100-200 chars. For run_python: 'Execute Python code in an isolated sandbox with resource limits. Returns stdout, stderr, and exit code. Use for data processing, calculations, or testing. Requires --enable-python flag.' For delete_file: 'Permanently delete a file from the workspace. This action cannot be undone. Requires explicit confirmation via a separate confirm_delete tool.'
• Document output schemas for all tools. E.g., list_files should return {files: [{name: string, size: int, modified: ISO8601}], total: int}. read_file should return {content: string, encoding: string, size: int}.
• Add tool annotations: mark list_files, read_file as readOnlyHint=true; mark run_shell, delete_file, write_file as destructiveHint=true; mark run_python, run_javascript as idempotentHint=false (side effects possible).
• Implement a confirm_delete tool that returns a confirmation token, then require that token in delete_file. This prevents accidental deletions from agent retry loops.
• Add timezone validation: declare timezone as enum with common IANA values (America/New_York, Europe/London, Asia/Shanghai, UTC) or a regex pattern matching IANA format. Include error guidance: 'Invalid timezone. Use IANA format (e.g. America/New_York). Call list_timezones() for options.'

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

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