[to #12345678] docs: update excludeTools documentation in extensions …

[Willam2004]

…guide

• Added clarification that tools specified in excludeTools will be disabled for the entire conversation context
• Added note that excludeTools configuration affects all subsequent queries in the current session

This change improves documentation clarity for extension developers by better explaining the scope and impact of the excludeTools configuration.

TLDR

This PR updates the documentation to clarify that the excludeTools setting applies globally across the entire conversation session—not just the current turn. This helps extension developers avoid unexpected behavior when configuring tool exclusions.

Dive Deeper

Previously, the documentation did not explicitly state that excludeTools has a session-wide effect. Developers might have assumed the exclusion was limited to a single query or turn, leading to confusion or bugs. This update adds two concise sentences to make the behavior unambiguous, aligning the docs with the actual runtime behavior.

No code changes—only documentation improvements in the developer guide.

Reviewer Test Plan

Since this is a documentation-only change:

• Reviewers should verify that the added sentences are clear, accurate, and consistent with the system’s actual behavior.
• Confirm that the wording matches the project’s documentation style (e.g., tone, terminology).
• No runtime testing is required, but reviewers may optionally build the docs site (if applicable) to ensure formatting renders correctly.

Testing Matrix

	🍏	🪟	🐧
npm run	✅	✅	✅
npx	N/A	N/A	N/A
Docker	N/A	N/A	N/A
Podman	-	-	-
Seatbelt	-	-	-

✅ = Verified that docs build successfully and changes appear as expected
N/A = Not applicable for documentation-only changes

Linked issues / bugs

[pomelo-nwu]

LGTM

[pomelo-nwu]

@Willam2004 Thanks for your contribution！