Browse all available brands/carriers for a country: gift cards (500+ US brands) and mobile top-up carriers (100+ countries). Never creates an order.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Filter by product type | |
| country_code | Yes | ISO country code, e.g. "us", "mx" |
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| brands | No | ||
| country | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry readOnlyHint=true and destructiveHint=false; the description reinforces and extends this with 'Never creates an order' and adds concrete scope details like 500+ US brands and 100+ countries. This is useful context beyond the annotations without contradiction.
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?
Two short sentences with the purpose front-loaded. The safety clarification 'Never creates an order' earns its place and every clause adds useful information without repetition.
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 simple two-parameter browse tool with 100% schema coverage, clear annotations, and an output schema present, the description provides everything needed to invoke it correctly. No gaps for callers.
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?
Schema description coverage is 100%, so the baseline is 3. The description adds value by giving examples of product types ('gift cards' and 'mobile top-up carriers') that map to the kind parameter, and 'for a country' reinforces the country_code parameter.
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?
States the verb 'Browse' and resource 'brands/carriers for a country,' and gives concrete categories (gift cards, mobile top-up carriers). The line 'Never creates an order' explicitly separates it from order-related siblings.
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?
Clearly signals when to use it: when browsing brands/carriers for a country. The 'Never creates an order' note provides an explicit when-not that disambiguates from order tools, though it does not name an alternative like search_products.
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.
Most tools have clear distinct purposes: listing currencies, payment methods, prices, brands, eSIM plans, products, searching, validating, creating, and checking order status. However, potential confusion between list_esim_plans and list_products for eSIM purchases, and search_products overlapping with list_brands/list_products, creates slight ambiguity. purchase_wizard serves as a fallback but is clearly labeled.
Tools follow a consistent verb_noun pattern: get_currencies, get_order_status, get_payment_methods, get_price, list_brands, list_esim_plans, list_products, validate_order, create_order, search_products. 'purchase_wizard' deviates slightly as a noun phrase rather than verb_noun, but it's a distinct standalone tool.
With 11 tools covering the full purchase lifecycle (browse, search, price, validate, create, status) plus payment configuration, the count is well-scoped for a payment/order platform. Each tool serves a necessary function without redundancy.
The tool surface is comprehensive: listing brands/products/eSIM plans, searching, getting prices and methods, validating and creating orders, and checking status. The flow from validate_order → create_order → get_order_status is complete, with fallback purchase_wizard covering widget-less scenarios. No major gaps.
