When your MCP tool list grows, treat it as an API surface instead of a feature…

When your MCP tool list grows, treat it as an API surface instead of a feature checklist. Lots of thin, loosely specified tools bloat context and force the model to guess which to call, so trim the surface to outcome-level tools per workflow, enforce tight parameter schemas (literal types, small param sets), and return lean, decision-first responses. Measure each tool like a public API—call frequency, retry patterns, and token cost—and refactor or remove any that don’t justify their invocation.