Three tools with minimal schema documentation and weak descriptions. Tool names lack action verbs (retrieve, repl_coder, repl_drawer are vague). Input schemas present but parameters lack type constraints and validation guidance. Descriptions are generic and do not explain when/why to use each tool or what happens on error. No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges, formats). Security risk: repl_coder executes arbitrary Python code with no sandboxing or permission checks visible.

• Rename tools with action verbs: 'search_knowledge_base' (not 'retrieve'), 'execute_python_code' (not 'repl_coder'), 'generate_graph' (not 'repl_drawer').
• Document output schemas for each tool. E.g., retrieve returns {results: [{title, content, score}], total_count}. repl_coder returns {stdout, stderr, exit_code}.
• Add parameter constraints: keyword must be 1-500 chars; code must be valid Python; include examples of valid inputs in descriptions.
• Implement sandboxing for repl_coder: restrict filesystem access, disable network calls, set execution timeout (e.g., 30s), return clear error on timeout or security violation.
• Add error handling guidance: 'If query returns no results, try broader keywords or check knowledge base is loaded. If code fails, error message will show line number and exception type.'

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

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