If you have built more than one AI tool in the past twelve months, you have noticed the same thing I have: the surface area of “how a model talks to systems” has exploded. Skills, MCP servers, CLI tools, Computer Use, function calling, declarative agents, custom engine agents, apps, actions, extensions, gems — every vendor uses a slightly different word for what looks like the same thing on a marketing slide. This is the AI tooling surface, and they are not the same thing. The trade-offs are real, the choice changes architecture, and picking the wrong part of the AI tooling surface wastes weeks.
This post is the mental model I now apply by default when I sit down to build something agentic and map it onto the AI tooling surface. It is opinionated. It is not a feature comparison. The goal is to help you decide which part of the AI tooling surface to reach for first, not to memorise the spec of each one.
I’ll cover seven surfaces (the original five, plus two that are too important to skip in 2026), map them across Anthropic, OpenAI, Microsoft, and Google terminology, and give you the decision tree I actually use to navigate the AI tooling surface.





