Check whether a merchant domain runs an ARC-compliant catalog (KaliCart Bridge). Returns bridge_version, merchant discovery URL and federated-indexing consent flags. A miss schedules a background probe. Use when you already know a merchant domain (verify ARC support, get its discovery URL); to discover products across merchants, use global_search.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Merchant domain, e.g. shop.example.com |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that a miss schedules a background probe, a behavioral side effect beyond the readOnlyHint and openWorldHint annotations. It also describes return contents, providing meaningful context without contradicting annotations.
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 concise sentences front-load the core action and return value, then add usage context and sibling differentiation. Every sentence adds value with no redundancy.
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 lookup tool with one well-documented parameter, the description fully covers purpose, returns, side effects, and usage context. No output schema exists, but the description enumerates what is returned, making it complete.
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% for the single parameter 'domain', with a clear example. The description adds no extra parameter semantics beyond the schema, but this is not needed given the schema's completeness, so baseline 3 is appropriate.
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 states the tool's primary action ('Check whether a merchant domain runs an ARC-compliant catalog'), specifies the return values (bridge_version, discovery URL, consent flags), and explicitly contrasts with global_search, distinguishing it from 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?
Provides explicit usage criteria ('when you already know a merchant domain') and names the alternative tool for product discovery ('use global_search'), giving clear when-to-use and when-not-to-use guidance.
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: product detail retrieval, global search, category listing, merchant listing, and merchant ARC verification. No two tools overlap in function.
Most tools follow a verb_noun pattern (get_product, list_categories, list_merchants, lookup_merchant), but 'global_search' deviates from that pattern by leading with an adjective rather than a verb. Scores are minor and readability remains high.
With 5 tools, the server is well-scoped for a federated commerce search catalog. Each tool earns its place without redundancy or bloat.
The surface covers the essential workflows: searching for products, retrieving product details, discovering categories and merchants, and verifying a merchant's ARC compliance. No obvious gaps for the stated purpose.