Document available Claude Code tools with descriptions and configuration

[RichardAtCT]

Add docs/tools.md with a comprehensive reference for all 15 default tools,
including descriptions, icon mappings, verbose output behavior, and security
layers. Update README.md and docs/configuration.md to link to the new reference.

https://claude.ai/code/session_01QFqmYhrY3ZHLwevHHqGnyu

[FridayOpenClawBot]

PR Review
Reviewed head: 88892f0b3a048c149d8faf11bffe22ebf78d3dc6

Summary

• Adds docs/tools.md as a comprehensive reference for available Claude tools, verbose behavior, and security layers.
• Updates config/docs/examples to include TaskOutput in allowed tools and links readers to the new docs page.
• Includes minor runtime updates (icon mapping + allowlist defaults) plus a broad poetry.lock refresh.

What looks good

• Good docs addition overall — this closes a real discoverability gap around tool names, behavior, and config knobs.
• Nice consistency work wiring TaskOutput through .env.example, settings.py, and admin help text.
• The security-layers section in docs/tools.md is useful and practically oriented.

Issues / questions

1. [Important] docs/tools.md vs README.md — docs/tools.md says “By default, the bot allows 16 tools”, while README says “16 configurable tools”, but the source set in src/config/settings.py appears to be 16 only after adding TaskOutput. Please confirm this count stays source-of-truth-driven; otherwise docs can drift quickly. Consider generating the list/count from code in CI or at least adding a docs check.
2. [Important] docs/tools.md (“Bash command validation (classic mode)”) — the text states dangerous patterns (including pipes/redirections/subshells) are blocked. If this is not universally true across all run modes/configs, this could create misleading security expectations. Recommend tightening wording to “by default / in classic mode only” everywhere that mentions these constraints (some sections already do, some read absolute).
3. [Nit] poetry.lock — this PR bundles a large lockfile/toolchain change (Poetry 2.1.3 -> 2.3.2, Python markers to ^3.11) that seems unrelated to tool documentation. Suggest splitting it into a separate dependency/toolchain PR for cleaner review and safer rollback.

Suggested tests (if needed)

• Add a small test/assertion that TaskOutput is present in default allowed tools and (if applicable) icon mapping metadata.
• Add a docs consistency check (script/test) that validates documented tool names/count against settings.py defaults.

Verdict

• ⚠️ Merge after fixes