Resolve a merchant's website domain to their Agenticfeed merchant ID and confirm they publish an Agentic Feed. Call this first when you only know a store's domain; use the returned merchant_id with get_product or the discovery feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Merchant website domain or URL, e.g. "boardgameextras.co.uk". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses core function but lacks details on edge cases (e.g., domain not found) or potential external calls.
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 sentences, front-loaded with main purpose followed by usage guidance. No waste.
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?
Given simple tool with one param and no output schema, the description adequately covers purpose and usage. No gaps.
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 coverage is 100% with clear description. The description adds an example ('boardgameextras.co.uk') but no extra semantics beyond the schema.
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 uses specific verb 'resolve' and resource 'merchant ID via domain'. It clearly distinguishes from sibling tools like get_product.
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?
Explicitly states when to use ('call this first when you only know a store's domain') and what to do next ('use returned merchant_id with get_product'). No exclusions but clear context.
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 has a clear, distinct purpose: find_merchant resolves merchant identity, get_product fetches product details, list_products enumerates products, and search_products finds products by intent. No overlap.
All tool names follow a consistent verb_noun pattern with underscores (find_merchant, get_product, list_products, search_products), making them predictable and easy to understand.
With 4 tools covering merchant discovery, product listing, detail retrieval, and intent-based search, the count is well-scoped for a product feed server and neither too few nor too many.
The set covers key read operations for a product feed, but lacks tools for browsing merchants without a prior domain or for updating/deleting products, which are minor gaps given the intended scope.