docs: Improve AsFunctionTool Disclaimers

[Mahdi Azarboon (azarboon)]

Motivation & Context

I've created this new and improved PR based on westey (@westey-m) recommendation in #3008. He has already approved the content in that PR, and I'm now updating the location so you can proceed with the merge.

---

Function tools are ideal for scenarios where determinism and predictability are critical, helping users avoid potential issues. This aspect is not currently documented on GitHub or Microsoft Learn. Since this example demonstrates a Function Tool, this update addresses that gap by highlighting potential use cases and benefits of this approach. The current example is simple and may cause users to underestimate the advantages of using Function Tools.

Description & Review Guide

This update is purely documentation and introduces no code changes. It adds content clarifying the use cases and potential benefits of Function Tools to guide users effectively.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

Pull request overview

Clarifies use cases for exposing .NET agents as function tools.

Changes:

• Adds guidance on function-tool scenarios and agent composition.

---

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

[Mahdi Azarboon (azarboon)]

Roger Barreto (@rogerbarreto) Thanks for your feedback. I’ve incorporated your suggestions. Could you please proceed with merging the PR?

[Mahdi Azarboon (azarboon)]

Roger Barreto (@rogerbarreto) i think its now ready to merge.