OpenYak exposes 7 tools with mixed quality. Tool names follow verb_noun convention (ListMcpResources, ReadMcpResource, McpAuth, MCP, BashTool, FileReadTool, FileEditTool), but descriptions are inconsistent. Most tools have basic descriptions (10-50 chars), below the 194-char baseline for production tools. Input schemas are present but sparse: parameters lack detailed descriptions explaining constraints, formats, or dependencies. BashTool has the most comprehensive schema with enum constraints (filesystem_mode), but others like MCP accept generic 'arguments' object with minimal guidance. No output schemas documented. Error handling is absent, no recovery guidance, retryability classification, or actionable error messages. Security concerns: BashTool exposes 'dangerously_disable_sandbox' as a parameter (should be server-side config), and FileEditTool lacks path traversal validation hints.

• Document output schemas for all tools. E.g., ListMcpResources should return {resources: [{name: string, uri: string, description: string}], total: number}.
• Expand parameter descriptions to 50-150 chars. For McpAuth.status, explain each enum value: 'disconnected: server not connected; connecting: handshake in progress; connected: ready to call tools; auth_required: credentials needed; error: connection failed'.
• Move 'dangerously_disable_sandbox' from BashTool parameters to server-side configuration. If agents need sandbox control, use a read-only 'sandbox_enabled' output field instead.
• Add error handling guidance: 'If ReadMcpResource returns 404, call ListMcpResources to discover available URIs.' Include retryability hints for transient failures.
• For MCP tool, either document the expected arguments schema for each downstream tool or split into separate tools per MCP server (e.g., CallGithubTool, CallSlackTool) with explicit schemas.