Single tool 'dynamic_openapi_tools' has critical definition gaps. Input schema is declared as empty object with dynamic generation promise, but no actual schema is visible in source code, only a description stating schemas are 'dynamically generated per operation.' Tool description is generic (98 chars) and lacks specificity about what operations are available, when to use this tool, or what it returns. No parameter descriptions visible. No output schema documented. The tool name itself is vague ('dynamic_openapi_tools' vs action verbs like 'call_openapi_operation'). Code shows OperationMeta registry and tool generation logic, but the actual tool registration with MCP is not visible in the provided source, only inference from tool_caller.py.

• Rename tool to 'call_openapi_operation' or 'invoke_api_endpoint' and add action verb. Update description to: 'Call any operation from the loaded OpenAPI specifications. Provide the operation ID (e.g., 'get_user', 'create_ticket') and required parameters. Returns structured response with status, data, and error fields.'
• Generate and expose per-operation tool definitions instead of a single dynamic tool. Each OpenAPI operation (get_user, create_ticket, etc.) should be a separate MCP tool with its own schema, description, and parameter docs. This enables LLM tool selection without guessing.
• Document output schema: define common response fields (status: 'success'|'error', data: object, error: {code, message, details}). Include pagination fields if applicable (total_count, next_cursor, limit).
• Add parameter descriptions to the schema. For each parameter location (path, query, header, body), document type, format, constraints, and whether it is required. Example: 'user_id (path, required, string): The unique identifier of the user to fetch.'
• Implement error recovery guidance. When an operation fails, return actionable error messages: 'Invalid operation_id: got "get_usr". Did you mean: get_user, get_users, get_user_profile?' This enables LLM self-correction.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry