Forbin is a meta-tool for testing remote MCP servers, not a domain-specific tool suite. Its 3 tools (list_tools, call_tool, get_tool_parameters) are intentionally generic wrappers. However, they suffer from critical definition gaps: descriptions are present but minimal (10-50 chars, below the 50-200 char LLM-optimized baseline); input schemas lack proper type definitions and parameter descriptions; output schemas are undocumented. The call_tool parameters object is untyped and undescribed. Error handling is absent, no guidance on what happens when a tool call fails or parameters are invalid. These gaps are severe for a tool that agents will invoke repeatedly.

• Expand tool descriptions to 80-150 chars. Example: 'list_tools: Fetch all available tools from the remote MCP server, including their names, descriptions, and input schemas. Call this first to discover what the server can do.'
• Document output schemas for all tools. Example: 'list_tools returns {tools: [{name: string, description: string, inputSchema: object}], total: number}.'
• Add nested schema for call_tool's 'parameters' field: {type: 'object', additionalProperties: true, description: 'Key-value pairs matching the target tool\'s inputSchema. Validate against the tool\'s schema before passing.'}'
• Add error handling guidance: 'If call_tool fails, the response includes {error: string, recovery: string}. E.g., error: "Tool not found", recovery: "Call list_tools() to see available tools."'
• Describe get_tool_parameters' 'tool' input: {type: 'object', required: ['name', 'inputSchema'], properties: {name: {type: 'string'}, inputSchema: {type: 'object'}}, description: 'A tool object from list_tools() output.'}