Comment by behnamoh
5 days ago
I cannot believe all these months and years people have been loading all of the tool JSON schemas upfront. This is such a waste of context window and something that was already solved three years ago.
5 days ago
I cannot believe all these months and years people have been loading all of the tool JSON schemas upfront. This is such a waste of context window and something that was already solved three years ago.
^ this. Careful design of what tools are passed when is key to good agent design.
What is the right pattern? Do you just send a list of tool names & descriptions, and just give the agent an "install" tool that adds a given tool to the schema on the next turn?
- claudes tool search tool - list of skills (markdown files) the agent can grep - claude skills - context compaction - sub-agents - plans
There is no one “right” pattern. But yes it all generalizes to context engineering.
With plans for example, you write out potential distractions for later, to keep (the AI and the Human context) focused on a task at hand.
That pattern solves a distinctly different use case than the skills folder, but plans can also refer to skills in specific ways.
Context engineering is evolving with overlapping complementary patterns, and while certain vendors are branding patterns, i think we will hopefully we see tools converge.
Solved how?
Function calling is back