test: cover empty tool results

[nightcityblade]

Related Issues

• Fixes Add regression coverage for ToolInvoker with empty tool results #12455

Proposed Changes:

Add parameterized regression coverage for tools that successfully return an empty string, list, or dictionary. The tests exercise both synchronous and asynchronous invocation and verify serialization, success status, and tool-call correlation.

How did you test it?

• hatch run test:unit test/components/agents/test_tool_calling.py -q — 71 passed
• hatch run pre-commit run --files test/components/agents/test_tool_calling.py — all hooks passed
• hatch run fmt test/components/agents/test_tool_calling.py — passed, unchanged

Notes for the reviewer

This is test-only regression coverage; runtime behavior is unchanged.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes through this linked PR.
• I have added unit tests; docstring updates are N/A because no production API changed.
• I've used the test: conventional commit type for my PR title.
• Documentation is N/A because this PR changes regression tests only.
• A release note is N/A because this test-only PR has no user-facing change.
• I have run pre-commit hooks and all applicable hooks passed.

[vercel]

Someone is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

nightcityblade seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[HaystackBot]

Hi @nightcityblade, thanks a lot for your contribution! 🙏

We noticed that the Contributor License Agreement (CLA) check (license/cla) hasn't passed yet, so we've temporarily moved this PR to draft and paused the review assignment.

To get your PR reviewed, please sign the CLA via the link in the license/cla check below (or in the CLA bot comment). As soon as the check turns green, this PR will automatically be marked ready for review again and a reviewer will be re-assigned.

[HaystackBot]

Hi @nightcityblade, just a friendly reminder: this PR is still in draft because the Contributor License Agreement (CLA) hasn't been signed yet. We'd love to review your contribution! Please sign the CLA via the link in the license/cla check, and this PR will automatically be marked ready for review.