How AI Agents Find Tools and Hand Off Work
AI-generated content — This article was generated using artificial intelligence and editorially reviewed for publication. Learn more.
Two coding agents are preparing release notes. One knows which pull requests shipped. The other has the writing checklist and a list of changes from an earlier conversation. Both can produce a plausible draft. The team still needs one answer it can verify against the release.
Between November 16 and 19, 2026, GitHub, Google, and Vercel each shipped something that addresses part of this problem. They cover three decisions you can make in any agent workflow: how to give an agent the right instructions, which tools to load, and what to leave behind for the next person or agent.
GitHub MCP Server can offer skills that match its toolset
GitHub MCP Server 2.2.0 adds filtered workflow skills to the local server. The feature is opt-in, and the server filters the skill catalog against the tools available to the connection. A restricted toolset can therefore expose fewer workflows. Check that your client supports MCP Skills and that the expected skill appears with your actual configuration. Release notes · GitHub MCP Skills documentation
This matters when you design a skill around a limited connection. For release notes, the agent needs to read the release tags and pull requests. Write the procedure so it can still produce a reviewable draft when publishing tools are unavailable. If the comparison data is missing, the draft should say which tags or pull requests are needed. Tool permissions continue to come from the connection. GitHub’s implementation notes
Gemini loads tool schemas when a task needs them
On November 19, Google added Tool Retrieval in preview for the Gemini Interactions API. You can defer a tool’s full parameter schema and let Gemini search for it as needed. Google documents support for function tools and remote MCP servers, with an option to run your own retrieval logic. The feature requires the v1beta Interactions API. Release notes · Tool Retrieval guide
Start with two requests against the same fixture. In the first, ask for the pull requests between two known tags and check that the right read tool was selected. In the second, supply the verified list up front and ask for a summary. The expected result is a draft with zero tool calls. Measure those outcomes before comparing token use or latency.
Vercel Board gives agents a place to leave evidence
Vercel announced Board on November 18 as an experimental shared message board for people and agents. It groups task updates in threads and supports channel-level access controls. Threads can sync with services such as GitHub and Slack through Vercel Connect. Before enabling sync, check who can read the destination. Vercel announcement · Board documentation
The thread can carry the facts a reviewer needs to pick up the work. A task marked complete tells you where to look. The tag range and pull request links let you check what actually shipped.
Try a release-note handoff in a sample repository
Use a sample repository with two tags, one merged pull request included between them, and one still open. Have the first agent prepare the draft with read access. Give a second agent only the handoff below and ask it to verify the draft against the repository.
| Record | Example |
|---|---|
| Scope | Changes between v1.3.0 and v1.4.0 |
| Evidence | Pull request #42 merged in range. Pull request #43 is still open. |
| Draft | The change from #42, with a link back to the pull request |
| Next action | A reviewer verifies the draft before publication |
The reviewer passes the exercise if it can explain why #43 stays out and trace the draft's claim for #42 to its source. Repeat with a missing tag. The expected result is a request for the tag, with the draft marked incomplete. Use the same fixture when you change a skill, expand the toolset, or introduce a shared board. SkillsLLM guide to testing AI skills
Sources checked November 22, 2026. The release-note exercise is a proposed test using sample data. Product details are from the linked official releases and documentation.