Chat Studio exposes 3 MCP client tools with critical definition gaps. Tool names lack action verbs (listMcpTools, callMcpTool, invalidateMcpSession use camelCase instead of verb_noun convention). Descriptions are present but minimal (10-40 chars). Input schemas are partially visible: callMcpTool has a basic schema with toolName and toolArguments, but parameter descriptions are generic. No output schemas documented. Error handling is absent, no guidance on recovery or categorization. The server acts as an MCP client wrapper rather than exposing domain-specific tools, limiting practical utility.

• Rename tools to snake_case with clear action verbs: list_mcp_tools, call_mcp_tool, invalidate_mcp_session. Align with baseline convention (90% of A+ tools start with action verb).
• Expand descriptions to 50-200 chars. Example: 'List all available MCP tools from configured servers. Returns tool name, description, and input schema. Call this first to discover what tools are available before invoking call_mcp_tool.'
• Document output schemas for all tools. listMcpTools should return {tools: [{name: string, description: string, inputSchema: object}]}. invalidateMcpSession should return {success: boolean, message: string}.
• Replace generic 'toolArguments: object' with structured schema. Require a description like 'Arguments object matching the tool's inputSchema. Keys and types depend on the specific tool being called.'
• Add error handling with recovery guidance. Example: 'If tool not found, call list_mcp_tools to see available tools. If arguments invalid, check the tool's inputSchema for required fields and types.'