[Bug]: DotsToolParser drops tool calls when request.tools is None and crashes on FunctionTool

Finding: In vLLM main at commit 5281e49 (per the reporter), DotsToolParser in vllm/tool_parsers/dots_tool_parser.py is reported to behave incorrectly in two ways during tool call extraction. This is an external report, not reproduced by KFA, and the cause is not maintainer-confirmed. Source: https://github.com/vllm-project/vllm/issues/60865 Reported symptom 1: when the parser is constructed with its own tools list but the request has tools=None, the known tool-name set is reportedly empty. Well-formed dots_function_call blocks are then returned as ordinary text (tools_called=False, empty tool_calls) instead of parsed tool calls. The reporter's reproducer uses a ChatCompletionRequest with tools=None and a get_weather tool passed to DotsToolParser (issue #60865). Reported symptom 2: when tools are supplied as OpenAI Responses API FunctionTool objects, which expose name and parameters directly, the parser reportedly raises AttributeError: 'FunctionTool' object has no attribute 'function'. The reporter says this surfaces as an unhandled 500 error in serving (issue #60865). Reporter's analysis (hypothesis, unconfirmed by maintainers): the parser consults only request.tools and hardcodes tool.function.name and tool.function.parameters. The reporter's expected behavior is a fallback to self.tools when request.tools is None, and using the shared _extract_tool_info helper from vllm.tool_parsers.utils so that both ChatCompletionToolsParam and FunctionTool work (issue #60865). Environment as stated: PyTorch 2.11.0, Python 3.14.2, Windows 10 / Linux, vLLM main at commit 5281e49. No released version is identified as affected. Fix status: a commenter, who is not a maintainer, says a fix with regression tests was submitted as PR #60868 (https://github.com/vllm-project/vllm/issues/60865#issuecomment-6083295689). The PR itself was not supplied, so its review, merge and release state are unknown. The reporter's claim of 13/13 passing tests is self-reported and not independently verified. Limitations: single reporter, no maintainer response, no KFA reproduction, no confirmed workaround. Treat the diagnosis as a lead for checking whether your dots parser deployment passes tools only to the parser or uses Responses API FunctionTool inputs, and check the status of PR #60868 before relying on any fix.