Conduit is a federation gateway, not a primary MCP server. The three demo tools (add, multiply, reset) are minimal stubs in docs/demo/downstreams.py, not production tools. Tool definitions lack rigor: 'multiply' has an empty schema object (no properties, no required fields); 'add' and 'reset' have minimal descriptions (under 20 chars); no parameter descriptions; no output schemas documented; no error handling guidance. The 'reset' tool is marked DESTRUCTIVE but has no confirmation pattern or permission gate. These are demo/test fixtures, not real tools, and score accordingly.

• Expand 'add' description to 50 - 150 chars: 'Add two integers and return their sum. Use this for arithmetic operations. Returns the result as an integer.'
• Add full schema to 'multiply': {"type":"object","properties":{"a":{"type":"integer","description":"First operand"},"b":{"type":"integer","description":"Second operand"}},"required":["a","b"]}
• Document output schema for all tools: e.g. add returns {"type":"object","properties":{"result":{"type":"integer"}}}
• Add confirmation pattern to reset: require a 'confirm' boolean parameter or return a dry-run result before executing.
• Add parameter descriptions to all tools: 'a: The first integer operand (range: -2^31 to 2^31-1)' and 'b: The second integer operand (range: -2^31 to 2^31-1)'

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

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained