Defining tool schemas and descriptions in Agentic AI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a tool schema with a name.

Agentic AI

tool_schema = {"name": "[1]"}

Drag options to blanks, or click blank then click option'

AToolOne

Bdescription

Ctool_name

Dschema

Attempts:

3 left

💡 Hint

Common Mistakes

Using a key instead of a string value for the name.

Leaving the value empty or not a string.

The 'name' key should be assigned the tool's name as a string, like 'ToolOne'.

2fill in blank

medium

Complete the code to add a description field to the tool schema.

Agentic AI

tool_schema = {"name": "ToolOne", "description": "[1]"}

Drag options to blanks, or click blank then click option'

AToolOne

Btool_description

Cdescription

DThis tool performs data cleaning

Attempts:

3 left

💡 Hint

Common Mistakes

Using a key name instead of a descriptive string.

Leaving the description empty.

The description should be a string explaining what the tool does.

3fill in blank

hard

Fix the error in the tool schema definition by completing the missing field.

Agentic AI

tool_schema = {"name": "ToolOne", "description": "Data cleaning tool", "parameters": [1]

Drag options to blanks, or click blank then click option'

A[]

BNone

C{}

D''

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list [] instead of a dictionary for parameters.

Using None or empty string which are invalid here.

The 'parameters' field should be a dictionary (empty or with keys) to define tool parameters.

4fill in blank

hard

Fill both blanks to define a tool schema with a name and a list of supported actions.

Agentic AI

tool_schema = {"name": "[1]", "actions": [2]

Drag options to blanks, or click blank then click option'

ADataCleaner

B["clean", "validate"]

C["run", "stop"]

DToolActions

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a list for actions.

Using an invalid name or variable instead of a string.

The name should be a string like 'DataCleaner' and actions a list of strings representing supported actions.

5fill in blank

hard

Fill all three blanks to define a tool schema with name, description, and parameters.

Agentic AI

tool_schema = {"name": "[1]", "description": "[2]", "parameters": [3]

Drag options to blanks, or click blank then click option'

AModelTrainer

BTrains machine learning models

C{"epochs": 10, "batch_size": 32}

D{"learning_rate": 0.01}

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list instead of a dictionary for parameters.

Mixing up description and name fields.

The name is 'ModelTrainer', description explains the tool, and parameters is a dictionary with settings like learning rate.

Practice

1. What is the main purpose of defining a tool schema in agentic AI?

easy

A. To describe what the tool does and what inputs it needs

B. To write the tool's source code

C. To train the AI model

D. To store user data securely

Solution

1. Step 1: Understand the role of tool schemas

   Tool schemas explain what a tool does and what inputs it requires for proper use.

2. Step 2: Differentiate from other tasks

   Writing code, training models, or storing data are separate tasks not covered by schemas.

3. Final Answer:

   To describe what the tool does and what inputs it needs -> Option A

4. Quick Check:

   Tool schema = tool description + inputs [OK]

Hint: Schemas explain tool purpose and inputs clearly [OK]

Common Mistakes:

• Confusing schema with code implementation
• Thinking schema trains the AI
• Assuming schema stores data

2. Which of the following is the correct way to define a tool schema description in JSON format?

easy

A. {"name": search, "desc": "Finds info", inputs: {query: string}}

B. {"tool": search, description: Finds info, inputs: query string}

C. {"name": "search", "description": "Finds information", "inputs": {"query": "string"}}

D. {name: "search", description: "Finds information", inputs: {query: string}}

Solution

1. Step 1: Check JSON syntax correctness

   {"name": "search", "description": "Finds information", "inputs": {"query": "string"}} uses proper JSON with keys and string values quoted correctly.

2. Step 2: Verify key names and structure

   {"name": "search", "description": "Finds information", "inputs": {"query": "string"}} uses "name", "description", and "inputs" keys properly with correct value types.

3. Final Answer:

   {"name": "search", "description": "Finds information", "inputs": {"query": "string"}} -> Option C

4. Quick Check:

   Valid JSON with quoted keys and strings = {"name": "search", "description": "Finds information", "inputs": {"query": "string"}} [OK]

Hint: Look for quoted keys and string values in JSON [OK]

Common Mistakes:

• Missing quotes around keys or strings
• Using unquoted identifiers
• Incorrect key names or structure

3. Given this tool schema snippet:

{"name": "calculator", "description": "Performs math operations", "inputs": {"operation": "string", "x": "number", "y": "number"}}

What would be the expected output if the tool is called with inputs {"operation": "add", "x": 5, "y": 3}?

medium

A. 8

B. "add"

C. 53

D. Error: missing inputs

Solution

1. Step 1: Understand the tool schema inputs

   The tool expects an operation (like add) and two numbers x and y.

2. Step 2: Apply the operation to inputs

   Adding 5 and 3 results in 8 as output.

3. Final Answer:

   8 -> Option A

4. Quick Check:

   5 + 3 = 8 [OK]

Hint: Match inputs to operation and compute result [OK]

Common Mistakes:

• Returning operation string instead of result
• Concatenating numbers as strings
• Assuming missing inputs cause error

4. You have this tool schema:

{"name": "translator", "description": "Translates text", "inputs": {"text": "string", "target_lang": "string"}}

Which error is present in this schema?

medium

A. Description is too long

B. Name key is missing

C. Input types should be numbers

D. Missing closing brace for inputs object

Solution

1. Step 1: Check JSON syntax carefully

   The inputs object is opened but not closed with a } before the schema ends.

2. Step 2: Verify other keys

   Name key exists, description length is fine, input types as strings are correct.

3. Final Answer:

   Missing closing brace for inputs object -> Option D

4. Quick Check:

   Unclosed braces cause JSON errors [OK]

Hint: Count opening and closing braces carefully [OK]

Common Mistakes:

• Ignoring missing braces
• Thinking input types must be numbers
• Assuming description length matters

5. You want to define a tool schema for a weather forecast tool that takes a city name and date, and returns temperature and conditions. Which schema correctly describes this tool?

hard

A. {"name": "weather", "description": "Forecast tool", "inputs": {"city": "string"}, "outputs": {"temp": "string", "cond": "string"}}

B. {"name": "weather", "description": "Provides weather forecast", "inputs": {"city": "string", "date": "string"}, "outputs": {"temperature": "number", "conditions": "string"}}

C. {"name": "weather", "description": "Gives weather", "inputs": {"location": "string", "day": "date"}}

D. {"name": "weather", "inputs": {"city": "string", "date": "string"}}

Solution

1. Step 1: Check completeness of schema

   {"name": "weather", "description": "Provides weather forecast", "inputs": {"city": "string", "date": "string"}, "outputs": {"temperature": "number", "conditions": "string"}} includes name, description, inputs (city and date), and outputs (temperature and conditions) as required.

2. Step 2: Verify input and output types

   Inputs are strings (city, date), outputs are number and string, matching expected data.

3. Final Answer:

   {"name": "weather", "description": "Provides weather forecast", "inputs": {"city": "string", "date": "string"}, "outputs": {"temperature": "number", "conditions": "string"}} -> Option B

4. Quick Check:

   Complete schema with inputs and outputs = {"name": "weather", "description": "Provides weather forecast", "inputs": {"city": "string", "date": "string"}, "outputs": {"temperature": "number", "conditions": "string"}} [OK]

Hint: Include inputs and outputs with correct types [OK]

Common Mistakes:

• Omitting outputs section
• Using wrong input/output keys or types
• Leaving out description