get_sandbox_inventoryUse this when an agent needs to describe the bounded synthetic inventory used by the challenge. Do not use it for real travel transactions or private data.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | ||
| caveat | Yes | ||
| routeMode | Yes | ||
| defaultRoute | Yes | ||
| containsPersonalData | Yes | ||
| supplierConnectivity | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is well covered. The description adds the 'bounded synthetic inventory' and 'not real/private' context, which aligns with the openWorldHint annotation. No additional behavioral details like return format are needed because an output schema exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. The usage condition is front-loaded, and the exclusion is stated immediately after. Every word adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only tool with annotations and an output schema, the description is complete. It tells the agent when to use the tool and what domain it covers, without omitting any critical invocation context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is no parameter burden for the description to carry. Per the baseline for zero-parameter tools, a score of 4 is appropriate since the description does not need to explain parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('describe') and resource ('bounded synthetic inventory used by the challenge'), making the tool's purpose immediately clear. It also distinguishes the tool from real travel transactions and private data, which prevents misuse.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit guidance: 'Use this when an agent needs to describe the bounded synthetic inventory.' It also gives a clear exclusion: 'Do not use it for real travel transactions or private data.' It does not explicitly name alternative sibling tools, but the context is strong enough for an agent to decide when this tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct facet of the challenge—capabilities, tool contracts, safety model, and inventory—so an agent can select without ambiguity. The repetitive 'do not use for real travel' phrasing does not obscure the clear differentiation.
All four tools follow a consistent get_<noun> pattern with clear, domain-specific nouns. Naming is predictable and uniform.
Four tools is well-scoped for an informational challenge-orientation server. Each tool earns its place by covering a necessary aspect without redundancy.
The set fully covers the challenge's public boundary, available contracts, safety rules, and synthetic inventory. There are no obvious missing operations for the stated purpose of describing the challenge environment.