Single tool 'get_weather' has critical definition gaps. Description is present but minimal (34 chars, below baseline 194). Input schema visible but incomplete: 'location' param has description, but 'user' param marked as 'object' with no field definitions and noted as 'excluded from tool definition', contradictory and non-functional. No output schema documented. No error handling guidance. Tool appears to be a mock/test fixture (file: agentflow/qa/testing/mock_tools.py), not production code. This is a test harness, not a real MCP server implementation.

• Document complete output schema: specify return type (object/string), all fields (e.g., temperature, condition, humidity, location), types, and descriptions.
• Expand tool description to 100-200 chars: 'Retrieves current weather conditions for a specified location. Returns temperature, conditions, and forecast. Use when user asks about weather. Requires valid location name or coordinates.'
• Fix 'user' parameter: either remove it if unused, or define it as a proper object with typed fields (e.g., user_id: string, user_name: string).
• Add error handling documentation: 'Returns error if location not found or API unavailable. Suggest alternative locations if exact match fails.'
• Move tool definition from test directory (agentflow/qa/testing/) to production code if this is intended as a real MCP server tool.