[dotnet-port-fixes] Execute invocable tool siblings

[Michelle Clayton (michelle-clayton-work)]

Summary

Updated agent/harness/toolautocall so invocable local tool calls still run when the same assistant turn also includes declaration-only schema tools. The middleware now executes the invocable siblings, leaves declaration-only calls actionable for the caller, and marks only the executed local calls informational-only. Added a regression test covering mixed-call ordering.

Ported .NET PRs

• .NET: Store executable function calls bypassed by declaration-only tool calls agent-framework#7388 - Store executable function calls bypassed by declaration-only tool calls. Ported the behavior correction from upstream commit aaaa56bc60b6703b305664f196e74b284e425918, based on dotnet/src/Microsoft.Agents.AI/ChatClient/InvocableFunctionBypassingChatClient.cs and dotnet/tests/Microsoft.Agents.AI.UnitTests/ChatClient/InvocableFunctionBypassingChatClientTests.cs.

Breaking Changes

No.

Tests and Examples

• go test ./agent/harness/toolautocall
• Added TestFunctionInvoking_MixedInvocableAndNonInvocableSchemaToolExecutesInvocableSibling
• No examples changed

Notes

• Kept the fix internal to agent/harness/toolautocall; no exported Go API changed.
• Preserved existing TerminateOnUnknownCalls behavior for unknown tools and only realigned mixed invocable/declaration-only schema-tool handling.

Generated by .NET to Go Fixes and Test Porting Agent · gpt54 · 212.2 AIC · ⌖ 12.4 AIC · ⊞ 24.2K · ◷

Closes #842

[Copilot]

Pull request overview

Updates the agent/harness/toolautocall middleware to correctly handle mixed assistant turns that contain both (a) invocable local function calls and (b) declaration-only (non-invocable) schema tool calls. The middleware now executes the invocable siblings, leaves declaration-only calls actionable for the caller, and only marks the executed local calls as informational-only, with a regression test covering the mixed-call ordering.

Changes:

• Added an execution-plan step to split function calls into “processable now” vs “terminate after processing” to avoid bypassing invocable siblings.
• Updated the main loop to use the plan for termination decisions and for selecting which calls to execute/mark informational-only.
• Added a regression test for mixed invocable + non-invocable schema tool calls to ensure invocable siblings still execute.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
agent/harness/toolautocall/autocall.go	Builds and uses a function-call execution plan so invocable siblings execute even when non-invocable schema tools are present.
agent/harness/toolautocall/autocall_test.go	Adds regression coverage ensuring mixed-call ordering executes the invocable tool and leaves declaration-only calls actionable.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Parity Review: ✅ Approved

This PR ports a behavior correction from the upstream .NET implementation (microsoft/agent-framework#7388, commit aaaa56bc) and stays semantically aligned with InvocableFunctionBypassingChatClient.cs.

Scope: Internal to agent/harness/toolautocall — no exported Go APIs were added, removed, or changed.

Parity check:

• ✅ Go fix mirrors the upstream .NET logic: invocable tool calls in a mixed turn (alongside declaration-only schema tools) are now correctly executed rather than bypassed.
• ✅ Declaration-only calls are left actionable for the caller, matching upstream semantics.
• ✅ TerminateOnUnknownCalls behavior is preserved unchanged.
• ✅ No analogous Python surface exists for this middleware layer; Python divergence is not a concern here.

No cross-repo consistency issues found. No public API surface changed — the public-api-change label is not needed.

Generated by Go API Consistency Review Agent for #863 · sonnet46 · 14.1 AIC · ⌖ 5.64 AIC · ⊞ 5.7K · ◷

[Quim Muntal (qmuntal)]

microsoft/agent-framework#7388 implements a new feature, it doesn't fix a bug, but the Go PR landed as part of the dotnet-port-fixes. AFAIU, this shouldn't have happened. Also, the port seems incomplete, as the .NET feature is opt-in.

[Michelle Clayton (michelle-clayton-work)]

Quim Muntal (@qmuntal) opened up #872 to improve the wording of the workflow prompts