Orkis demonstrates solid foundational tool design with clear naming conventions (verb_noun pattern: save_memory, search_memories, promote_artifact, run_shell_command, stage_artifact, get_utc_now, roll_dice). All 7 tools have descriptions (avg ~120 chars, within 10-1024 range). Parameter descriptions are present and reasonably detailed. However, critical gaps exist: no visible output schemas documented for any tool, parameter type definitions are inferred from code rather than explicitly visible in schema definitions, and error handling guidance is minimal. The codebase shows good architectural patterns (ISandboxedTool, ITool interfaces, ToolDescriptor records) but the actual JSON schemas and error recovery patterns are not evident in provided source.

• Document output schemas for all 7 tools. For search_memories, specify: {memories: [{id, text, scope, created_at}], total_count}. For run_shell_command, specify: {exit_code, stdout, stderr, duration_ms}. Include these in ToolDescriptor or a separate schema registry.
• Add error recovery guidance to run_shell_command: 'On timeout (>30s), retry with a shorter command or check system load. On permission denied, verify sandbox grant. On non-zero exit, stderr contains the failure reason.'
• Formalize parameter constraints: save_memory.scope as enum ['global', 'run']; search_memories.top_k with min=1, max=100; run_shell_command.command with length limit and injection guards.
• Implement confirmation pattern for run_shell_command: add optional 'dry_run' parameter (default false) to preview command without execution. Or require explicit 'confirm=true' for destructive patterns.
• Ensure promote_artifact returns {artifact_name, artifact_id, size_bytes, created_at} so stage_artifact can immediately reference it without a lookup call.