Google Agent Development Kit
Development framework for agents and multi-agent systems combining models, tools and testing. Provides building blocks instead of a ready-made directory of agents.
This profile summarizes the provider or project documentation. It is not a commercial ranking, independent certification or a guarantee of account-level availability. Versions and pricing change.
Purpose and operating environment
Development framework for agents and multi-agent systems combining models, tools and testing. Provides building blocks instead of a ready-made directory of agents.
This is a development or orchestration infrastructure. A developer must configure models, tools, access policy, deployment and testing: installing it alone does not create a reliable agent.
A practical application
Create two agents for retrieving documents and summarizing results with references.
Before starting, define the expected artifact, authorized data, success criteria and actions requiring approval. Keep source links or files. Compare claimed success to the actually observed outcome.
Before your first task
Read ADK documentation and complete the minimal agent tutorial before delegation.
Read setup prerequisites, licensing, model requirements and account restrictions on the provider site. Never paste API keys into a public page or a shared prompt.
Four steps for a controlled evaluation
- 01
Install the selected SDK
- 02
Describe tools and models
- 03
Test handoffs
- 04
Review traces and costs
Limitations and safeguards
External models and tools have their own limits, permissions and pricing; integration is not validation.
Evaluate answer quality, tool selection, permissions, reproducibility, total cost and prompt injection risk separately. If the agent can send, delete, pay or publish, require explicit confirmation and verify the outcome in the destination system.
- Authorized data and scope
- Actual actions and approval requirements
- Evidence, traces and rollback
- Maintenance, versions, accessibility and access terms
Documentation and references
Vendor documentation describes a product or project rather than serving as independent validation. The OWASP source covers general risks and does not mean OWASP tested or endorsed this tool.