How strands-agents/tools works
File structure
• Top‐level packaging:
• pyproject.toml (build + dependencies)
• src/strands_tools (each .py or sub-package is one tool implementation or common util)
• src/strands_tools/utils (shared helpers & model adapters)
• docs/ (static markdown docs and tool stability matrix)
• tests/ and tests_integ/ (unit vs. integration tests organized by tool domain)
• CI & release:
• .github/workflows (lint, unit tests, integration tests, PyPI publish)
• .pre-commit-config.yaml
• Naming patterns reveal a plugin architecture: one file or subfolder = one tool provider that registers itself with Agent.
Key insights from the README
• There is no monolithic backend or database; most tools either call external systems or operate locally.
• The library is intended to be installed via PyPI, used as from strands_tools import file_read, shell, use_aws, ….
• Tools are grouped by capability (I/O, compute, cloud, memory, messaging, scheduling, automation, etc.).
• Environment variables drive behavior, and a set of common utilities underpins multiple tools.