ask-for-toolslisted

# Ask for Tools When the agent is limited by tool boundaries rather than reasoning ability, proactively ask the user for tools instead of brute-forcing it. **What it can do:** - Identify the categories of tools the task may need (MCP server, CLI tools, Python/Node packages, API keys, permissions, local files). - Self-check whether a tool already exists, is loaded, or is configured before asking for it. - Make the request in a structured way: what is missing, why, what happens without it, and alternatives. - Give the user options: provide the tool / try a fallback / stop the task. - Remember the user's choice in the current conversation. **What it cannot do (without explicit authorization):** - Install system-level software or modify global configuration. - Create or modify persistent configuration files outside the current task context. - Assume the user has authorized a tool just because it was used before. - Bypass explicit approval to obtain API keys, tokens, credentials, or elevated permissions. **Default behavior:** - Ask before installing. The agent can check whether a tool exists, but will not automatically install system-affecting tools without approval. - When the user refuses to provide a tool, offer fallback or stop options instead of silently failing or repeatedly hitting the same dead end. - Keep each request concise; related tools can be grouped. - Explain why the tool is needed in plain language. ## Trigger Conditions 1. **At the start of a new task** — t