store_infoShipping costs and delivery times per EU country, free-shipping thresholds, 30-day return policy, payment methods and languages of Gameshop Enter.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It lists the information content but does not explicitly state that the tool is read-only, returns static reference data, or explain any limitations or freshness caveats. It is not misleading, but it adds limited behavioral context beyond the obvious.
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 a single, well-structured sentence that front-loads the most important content (shipping costs and delivery times) and then efficiently lists the remaining topics. Every phrase adds substantive information.
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 no-parameter, no-output-schema information tool, the description covers the main content categories an agent needs to decide whether to invoke it. It does not explicitly describe the response format, but that is a minor gap for a static store-info tool.
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 takes zero parameters, so the schema fully covers invocation needs. The description adds semantic context about the kind of information returned, which is useful for selection even though no parameter explanations are required.
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 clearly identifies the tool's purpose: it provides store policy information including shipping costs, delivery times, free-shipping thresholds, returns, payments, and languages. This is a specific, concrete resource and is easily distinguishable from the sibling tools focused on products, quotes, and searches.
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?
The description implies when to use this tool: when the agent needs store-level policies or reference information. However, it does not explicitly state alternatives or when not to use it, such as clarifying that it is not for product-specific queries.
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 serves a distinct function: product lookup, quote calculation, catalog search, and store information. There is no overlap in their purposes, so an agent can easily select the right tool for a given task.
All tool names follow a consistent verb_noun pattern: get_product, get_quote, search_products, store_info. The prefixes 'get_', 'search_', and 'store_' clearly indicate the action and resource, making the set predictable.
With only 4 tools, the server is tightly scoped to a storefront workflow: search, product details, pricing with shipping, and store policies. Each tool is necessary and the count feels right for the domain.
The set covers the essential customer journey: searching, viewing products, obtaining a quote with checkout URL, and accessing store info. A minor gap is the lack of direct order placement or cart tools, but those appear to be handled externally via the checkoutUrl, so the surface is reasonably complete.