Defining tool schemas and descriptions in Agentic AI - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Tool Schema Purpose

Why is defining a clear schema important when creating a tool description for an AI agent?

A It allows the AI agent to ignore the tool's inputs and focus on outputs only.

B It makes the tool run faster by optimizing its code automatically.

C It ensures the AI agent understands the tool's inputs, outputs, and usage constraints.

D It prevents the AI agent from using the tool in any context.

💡 Hint

Think about how an AI agent decides when and how to use a tool.

A clear schema defines what inputs the tool expects, what outputs it produces, and any rules for usage. This helps the AI agent use the tool correctly and safely.

❓ Predict Output

intermediate

Output of a Tool Schema Definition

What is the output of this Python code defining a simple tool schema dictionary?

Agentic AI

tool_schema = {
    "name": "calculator",
    "description": "Performs basic arithmetic operations",
    "inputs": {"operation": "str", "x": "float", "y": "float"},
    "outputs": {"result": "float"}
}
print(tool_schema["inputs"])

A {'result': 'float'}

B TypeError: unhashable type: 'dict'

C ['operation', 'x', 'y']

D {'operation': 'str', 'x': 'float', 'y': 'float'}

💡 Hint

Look at the key used inside the print statement.

The code prints the value associated with the key 'inputs' in the tool_schema dictionary, which is another dictionary describing input types.

❓ Model Choice

advanced

Choosing the Best Schema Format for Tool Description

Which data format is best suited for defining tool schemas to be used by AI agents for interoperability and easy parsing?

A Binary serialized objects without human readability

B JSON Schema with strict typing and validation rules

C Plain text with informal descriptions

D Unstructured XML without schema definitions

💡 Hint

Consider formats that support validation and are widely supported.

JSON Schema provides a structured, machine-readable format with validation capabilities, making it ideal for defining tool schemas for AI agents.

❓ Hyperparameter

advanced

Adjusting Tool Schema Complexity

When defining a tool schema for an AI agent, which hyperparameter adjustment helps balance between schema detail and agent performance?

A Adding precise data types and required fields only for essential inputs

B Increasing the number of input fields without constraints

C Removing all output descriptions to simplify the schema

D Using vague descriptions to allow flexible input types

💡 Hint

Think about how too much or too little detail affects the AI agent's ability to use the tool.

Adding precise data types and marking essential inputs as required helps the AI agent understand what is necessary without overwhelming it with unnecessary details.

🔧 Debug

expert

Debugging a Tool Schema Description Error

Given this tool schema snippet, what error will occur when an AI agent tries to parse it? { "name": "weather_tool", "description": "Fetches weather data", "inputs": { "location": "string", "date": "date" }, "outputs": { "temperature": "float", "condition": "string" }, "required": ["location", "time"] }

A KeyError because 'time' is not defined in inputs

B TypeError because 'date' is not a valid data type

C No error, schema is valid

D ValueError because outputs are missing required fields

💡 Hint

Check the required fields against the inputs keys.

The 'required' list includes 'time' which is not a key in the 'inputs' dictionary, causing a KeyError during validation.