Ratel Local exposes 4 tools with basic descriptions and schemas, but significant gaps limit production readiness. Tool names follow verb_noun convention (search_capabilities, invoke_tool, get_skill_content, auth), which is good. However, descriptions are minimal (10-60 chars), parameter descriptions are sparse or missing, and output schemas are not documented. The auth tool is defined in a UI file (ToolsPage.tsx), not the core server, suggesting incomplete tool registration. No evidence of error handling guidance, input validation rules, or pagination support. Schemas present but lack depth, parameters have types but descriptions are often single-word or absent.

• Expand tool descriptions to 100-200 characters. For invoke_tool: 'Execute a tool from the upstream MCP servers in the catalog. Requires toolId (from search_capabilities) and arguments object matching the tool's input schema. Returns the tool's result or an error with recovery guidance.'
• Document output schemas for all tools. E.g., search_capabilities should return {tools: [{id, name, description, inputSchema}], total, nextCursor}. invoke_tool should return {result, toolId, executedAt} or {error, retryable, suggestion}.
• Add parameter descriptions for all fields. 'arguments' in invoke_tool should be: 'Arguments object matching the target tool's input schema. See search_capabilities to discover available tools and their required parameters.'
• Move auth tool definition from UI to core server (packages/core/src/lib/server.ts) and verify it is registered with the MCP server. Confirm it is actually exposed as a callable tool.
• Add error handling guidance. E.g., invoke_tool: 'On failure, returns {error, toolId, retryable: boolean, suggestion: string}. If retryable, the agent may retry. If not, suggest search_capabilities to find an alternative tool.'