{"id":21969,"date":"2026-04-29T19:23:10","date_gmt":"2026-04-29T19:23:10","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/21969\/"},"modified":"2026-04-29T19:23:10","modified_gmt":"2026-04-29T19:23:10","slug":"cut-ai-token-usage-by-96-heres-how-aws-strands-agents-does-it","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/21969\/","title":{"rendered":"Cut AI token usage by 96%? Here’s how AWS Strands Agents does it."},"content":{"rendered":"

For this episode of The New Stack Makers, I sat down with AWS developer advocate Morgan Willis<\/a> to talk about Strands Agents<\/a>, the company\u2019s open source agentic framework, which has seen over 14 million downloads since it launched just under a year ago. Willis brought a hands-on demo built around a simple accounting API to show what building with Strands looks like in practice.<\/p>\n

The demo walks through three iterations of the same task: looking up the latest invoice for a customer. First, Willis mapped each API endpoint directly to an agent tool, the way most developers would by default. The agent needed five chained API calls and burned roughly 52,000 tokens. Then she swapped in intent-based tools that are built around an outcome rather than a data operation. With the same query, getting an answer now took one tool call and only 2,000 tokens.<\/p>\n

\u201cIt\u2019s calling multiple API\u2019s, but rolling them up into one intent-based tool for the agent that it\u2019s going to have a better time using \u2014 and understanding when exactly to use it. [\u2026] <\/p>\n

\u201cThe fewer tools that you expose to your agent, the less likely it is to call the wrong one.\u201d<\/p>\n

\u201cYour agent is going to have a better time reasoning around what tool to use and when, because these tools are more aligned to a task and less aligned to data,\u201d Willis tells The New Stack. \u201cThe fewer tools that you expose to your agent, the less likely it is to call the wrong one.\u201d<\/p>\n

The third iteration moved those tools to a remote MCP server via AWS Agent Core Gateway and enabled semantic search across the tool catalog, so the agent received only the tools relevant to each query, rather than the full set of 16. That cut token usage roughly in half again compared to loading everything.<\/p>\n

Willis says the broader principle at work here is that narrowly scoped agents tend to outperform general-purpose ones.\u00a0<\/p>\n

\u201cI think agents that are more narrowly defined tend to perform better than general use case agents. If you\u2019re looking for context efficiency, speed, and accuracy, I would also look at your agent design as well.\u201d\u00a0<\/p>\n

Having many agents, each doing a small number of things, lets you design tools precisely for each use case rather than building a more general agent that tries to do everything. As MCP servers proliferate and tool catalogs grow, the question of which tools an agent actually sees on a given run is going to matter as much as the tools themselves.<\/p>\n

\t<\/p>\n

\n\t\t\t\tYOUTUBE.COM\/THENEWSTACK\n\t\t\t<\/p>\n

\n\t\t\t\tTech moves fast, don’t miss an episode. Subscribe to our YouTube
\n\t\t\t\tchannel to stream all our podcasts, interviews, demos, and more.\n\t\t\t<\/p>\n

\t\t\t\tSUBSCRIBE<\/p>\n

\t<\/a><\/p>\n

Group
\n Created with Sketch.<\/p>\n

\t\t<\/p>\n

\t\t\t\t\t<\/p>\n

\n\t\t\t\t\t\t\tBefore joining The New Stack as its senior editor for AI, Frederic was the enterprise editor at TechCrunch, where he covered everything from the rise of the cloud and the earliest days of Kubernetes to the advent of quantum computing….\t\t\t\t\t\t<\/p>\n

\t\t\t\t\t\tRead more from Frederic Lardinois\t\t\t\t\t\t<\/p>\n

\t\t<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"For this episode of The New Stack Makers, I sat down with AWS developer advocate Morgan Willis to…\n","protected":false},"author":2,"featured_media":21970,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[405,13975,7537,3229,4898,2454],"class_list":{"0":"post-21969","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-agentic-ai","8":"tag-ai-agents","9":"tag-amazon-web-services-aws","10":"tag-artificial-intelligence-agents","11":"tag-podcast","12":"tag-post","13":"tag-video"},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/21969","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=21969"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/21969\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/21970"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=21969"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=21969"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=21969"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}