PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteBuild a data analyst agent by defining a narrow analysis job, giving a single ADK agent purpose-built tools, choosing where any analysis code will run, and evaluating the agent against realistic questions before deployment. A local prototype can validate the question-to-data path; Google Cloud deployment is a separate step, not a prerequisite for every first version.
1. Define the analysis job before writing code
Start with the questions the agent is meant to answer, the data it may use, and the actions it is allowed to take. Avoid framing the goal as “answer anything about our data”: a useful analyst agent has a bounded domain, known data paths, and a way to admit when a request cannot be answered from the available information.
As an Amazon Associate I earn from qualifying purchases.
Google’s Agents CLI development guide recommends deciding the problem, example questions, data sources, tools, authentication, safety constraints, success criteria, and whether the first milestone is a prototype or deployment before implementation: Agents CLI development guide.
- Questions: List representative requests, including routine calculations and requests that are ambiguous or outside scope.
- Data access: Identify the files or database the agent can reach and the credentials required. Grant only the access its job needs.
- Boundaries: Decide what data and operations are permitted, and what the agent should do when data is missing, unsuitable, or inaccessible.
- Success criteria: Define what counts as a correct answer: for example, a correct calculation, a useful explanation of assumptions, or a clear refusal when the data cannot support a conclusion.
2. Scaffold a prototype and begin with one agent
Use a minimal prototype to test whether the agent can understand the intended questions and obtain the right data. The CLI development guide documents scaffolding a prototype and adding deployment support later, so there is no need to commit to a hosted architecture before the core analysis path works: Agents CLI development guide.
For an initial analyst, one agent with a small set of purpose-built tools is often easier to reason about than a team of agents. ADK also provides sequential, parallel, and loop workflow agents, but those patterns are most useful when tasks divide into distinct responsibilities or require coordinated, iterative control. The CLI guide characterizes substantial tool integration as intermediate and long-running or multi-agent coordination as advanced. Choose the added orchestration only to solve a concrete workflow need: Agents CLI development guide and ADK workflow agents overview.
3. Give the agent tools designed for the data job
ADK custom tools can be plain Python functions added to the agent’s tools list. Their docstrings become descriptions the model uses to decide when and how to call them. Google’s manual tutorial puts the practical point plainly: “ADK tools are plain Python functions. The docstring becomes the description the LLM sees, so write it clearly — it tells the model when and how to use the tool.” Manual ADK tutorial
For an analyst, describe each tool’s purpose, inputs, permitted operations, and the form of its result. A narrow tool that returns a defined summary or calculation gives the agent a clearer contract than a vague tool that claims to analyze anything. Google’s overview treats function tools and orchestration as core ADK building blocks: ADK overview.
Choose a data path that fits the first task
A bounded file-analysis task and a database-backed workflow have different access and operational needs. Google’s community resource index lists a tutorial titled “How to Build a Data Science Agent with ADK,” described as covering database queries, Python analysis, and BigQuery ML. The index identifies it as community material, not content supported by Google or the ADK team, so treat it as an example to explore rather than an official implementation guarantee: ADK community resources.
4. Choose where analysis code executes
If a task calls for code-based, multi-step data analysis, Agent Runtime Code Execution is a documented sandbox option. Google’s documentation says it supports persistent state across multiple calls and data files up to 100MB; it identifies support in ADK Python v1.17.0. These limits and version details can change, so confirm the current documentation when implementing: Agent Runtime Code Execution documentation.
This is not a zero-setup local feature. The documented example requires a Google Cloud project with the Agent Platform API enabled, a sandbox environment, and an agent service account with the roles/aiplatform.user role. Follow the current official page for the exact setup and code because cloud requirements may change.
Keep the execution choice tied to the job. A local or otherwise minimal prototype can establish whether the agent’s question-and-data flow is useful; the managed sandbox is a distinct option for code execution with its own cloud prerequisites. Do not assume either location makes analysis inherently more accurate.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
5. Evaluate representative requests before deployment
ADK’s manual tutorial describes creating an evaluation dataset, configuring metrics, and running an evaluation command. The CLI development guide recommends an eval-and-fix loop: begin with a small set of core cases, fix failures, then expand the set. Manual ADK tutorial and Agents CLI development guide
Build test cases around the actual risks of your analyst’s job. These are suggested evaluation cases, not reported test results:
- A representative request with a known correct calculation.
- An ambiguous request, to check whether the agent asks for clarification rather than guessing.
- A request involving missing or unsuitable data, to check that it identifies the limitation.
- A tool or data-access failure, to check that it reports the problem instead of presenting an unsupported answer.
Use failures to improve tool descriptions, boundaries, data handling, or the agent’s response expectations. Expand the evaluation set as the scope grows; a successful demonstration on one prompt is not evidence that the agent handles the rest of its intended workload.
6. Deploy and observe only when the prototype is ready
The tutorial demonstrates adding a Cloud Run target, setting the project, deploying, and checking deployment status. It describes Cloud Trace as enabled by default in that flow, and separately describes provisioning infrastructure for prompt-response content logs: Manual ADK tutorial.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteTracing tool-call timing and recording prompt and response contents are different operational choices. Content logs may include user prompts or data outputs, so decide whether to enable them under the organization’s privacy and retention requirements; the tutorial’s setup steps do not establish what is appropriate for a particular organization.
If you later need a separate observability, prompt-management, or evaluation service, Freeplay’s official integration page describes those capabilities for ADK: Freeplay integration for ADK. It is an optional integration, not a requirement for building or deploying an agent.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
