[PratikDhanave (PratikDhanave)]

Partial implementation of #1139.

agenttool hardcoded a single query string argument with a fixed description. Add ArgName and ArgDescription config options so a caller can rename/re-describe the argument the model sees — mirroring the .NET/Python as-tool argument options.

Change

• Config.ArgName (default "query") and Config.ArgDescription (default "input query to invoke the agent").
• Schema() emits the configured argument name/description; Call() reads the configured key (decoding into a map rather than a fixed struct field).
• Defaults are unchanged, so existing behavior and tests are unaffected.

Scoped to the argument customization; session propagation (the other half of #1139) is left for the design discussion there, since obtaining the caller session at Call time needs a mechanism the tool interface does not currently expose.

Test

• TestNew_CustomArgNameAndDescription: a custom ArgName:"task" is reflected in the schema (and the default query is gone), and Call with {"task":...} forwards the value to the agent. Fails to build before the change (fields absent), passes after.

[Copilot]

Copilot review overview

🟡 Changes recommended

Invalid non-string argument values are silently converted into blank queries instead of returning decoding errors.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Preserve string type validation for configured tool arguments · New

What changed in this PR

Adds configurable argument names and descriptions to agenttool, preserving existing defaults.

Changes:

• Added ArgName and ArgDescription configuration.
• Updated schema generation and argument forwarding.
• Added custom-argument tests.

File	Description
tool/​agenttool/​agenttool.go	Implements configurable argument metadata and invocation.
tool/​agenttool/​agenttool_test.go	Tests custom schema and argument forwarding.

---

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

[Quim Muntal (qmuntal)]

https://github.com/microsoft/agent-framework-go/pull/1157/changes#r4068674786 needs fixings.

[Copilot]

🟡 Changes recommended

Exact map lookup introduces an undocumented case-sensitivity compatibility regression.

3 open findings

• Preserve case-insensitive JSON key matching in default decoding · New
• Preserve string type validation for configured tool arguments
• Remove cross-language porting history from Go API documentation · New

🧠 Review effort: Balanced

---

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

[github-actions]

API consistency review

Result	Scope
unable to determine	public API, user-visible behavior

Changed Go contract

agenttool.Config gains ArgName (default "query") and ArgDescription (default "input query to invoke the agent"). Schema() and Call() now use the configured argument name. Call() also matches the key case-insensitively and returns a JSON error if the value is not a string.

Upstream evidence reviewed

I could not complete the upstream comparison. Code search was rate-limited (429). The Python _agents.py file is about 195 KB and was returned as a single line, so I could not read the as_tool argument options. I also couldn't confirm the .NET AsAIFunction and AIFunctionFactoryOptions surface.

Assessment

The Go defaults are unchanged and match the existing .NET-aligned schema, so I found no confirmed divergence. I could not verify the following against upstream:

• the argument option names and defaults, including the Python as_tool arg_name and arg_description defaults;
• whether .NET exposes an equivalent option;
• whether case-insensitive key matching is expected.

Maintainers should check these manually. I removed parity-approved until that is done. public-api-change stays because exported config fields were added.

Generated by Go API Consistency Review Agent · copilot · auto · 27.5 AIC · ⌖ 0.616 AIC · ⊞ 4.9K · ◷