responses_tools.py DOX

Purpose

Own conversion of Agent Zero tool prompt files and MCP tool metadata into OpenAI Responses API function tool definitions.
Keep native Responses function availability synchronized with the text tool prompt surface.

responses_tools.py owns runtime implementation.
responses_tools.py.dox.md owns durable notes about responsibilities, prompt-derived contracts, and verification for this helper.

Build local function tools from enabled agent.system.tool.*.md prompt files and include vision_load only when the active chat model enables the matching vision prompt.
Local prompt-derived function names use existing bullet declarations that pair a backticked name with arg or args for multi-tool prompt files, otherwise prefer explicit "tool_name" examples, then the first prompt heading, and finally the prompt filename.
Apply registered tool-prompt render kwargs before deriving native metadata so descriptions never expose unresolved prompt templates.
Use an explicitly embedded JSON input schema when present. Infer only an unambiguous single backticked argument on an otherwise empty args: line; all other local tools receive an honest permissive object schema instead of prose-guessed types.
Native local-tool descriptions use the matching compact multi-tool declaration or the first prose line, not a duplicate copy of the full tool manual or fenced examples.
Preserve original Agent Zero tool names through the native Responses name map.
Keep MCP tool schemas merged after local prompt-derived tools.
Connector remote tools are advertised only when _a0_connector runtime metadata says the matching connected CLI capability is currently available.

Keep prompt-derived descriptions bounded by MAX_TOOL_DESCRIPTION_CHARS.
Treat plugin-specific tool gates as optional imports so core helper loading does not require a plugin that is absent or disabled.

Run targeted Responses/tool prompt tests after changing function-tool construction.
Run connector prompt gating tests when changing remote tool availability.