Skip to content

Blog

AI tool fatigue is a missing context layer

Teams count their AI tools when the list that decides is the second one: skills, commands, CLAUDE.md entries and context files. Where that list is rich, the tool list shrinks on its own.

Written by

Context engineering

Published: 11 August 2026 Updated: 1 min read

The AI tool fatigue posts keep coming up in my feed. I get why. But I think we’re counting the wrong list.

The first list is the tools

The first list is easy: AI channels in Slack, browser extensions, IDE integrations. A normal team has dozens of entries, and it takes five minutes to write them down. Whatever is on it looks different a year from now.

The second list is the context

The list that actually matters is the second one: skills, custom commands, CLAUDE.md entries, context files. These are the pieces that make whichever tool you’re using right now useful for your codebase specifically.

Honestly, the teams I see drowning in tool fatigue are almost always the same teams with nothing in the second list. No skills. No project-level conventions written down. No context layer the next tool can plug into.

A rich second list shrinks the first

When the second list is rich, the tool list collapses on its own. You stop chasing the next launch because the value isn’t in the launch. The value is in the context layer you’ve already written down, and any decent tool slots into it.

When the second list is empty, every new tool feels essential. It has to. There’s nothing else doing the work.

Ask what to write down before you prune

So the question I’d ask before pruning tools isn’t “which one do I cut?” It’s “what would I need to write down so the next tool would just slot in?” It’s the same question, one layer deeper.

If you can’t articulate the team’s context, agreements and conventions, no amount of pruning will fix the fatigue. And if you can, you probably won’t notice the count anyway.

What’s in your second list?

Further reading

  1. Feed the factory the decisions nobody wrote down In most organizations the knowledge that matters most is decided out loud in meetings and never written. Five concrete steps route it into the context layer the factory reads. 2 min readShort post
  2. Your coding agent is a free audit of your documentation Code generation is solved, so the constraint is now context. Every wrong answer an agent gives points at a standard the team knows and never wrote down. 2 min readShort post
  3. Context engineering is the standardization you could never sell Preparing context for AI agents forces the documentation and standardization architecture teams have pushed for years. The agent does not need it more than the organization did. It removes the resistance. 1 min readShort post

All 16 posts on Context engineering

ClientsCase study: A large DIY retailer in Germany

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Developers and QA
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check