List WooCommerce merchants participating in the KaliCart Global federated catalog. Returns merchant domain, storefront URL, and product count. Use before global_search to understand catalog coverage.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max merchants to return (default 20, max 50), ordered by product count desc. No pagination |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds value by specifying return fields and the federated catalog scope, but doesn't disclose potential rate limits, ordering details (only in schema), or any other behavioral traits beyond what annotations provide.
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, front-loaded sentences with no wasted words. The first sentence states the action and scope, the second gives return fields and a usage hint. Excellent structure.
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 straightforward list tool with one well-documented parameter, the description provides essential context: what is listed, what is returned, and when to use it. Since there is no output schema, the explicit mention of return fields adds completeness. It doesn't need to explain more.
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% for the single parameter 'limit', which already documents default, max, ordering, and lack of pagination. The tool description does not add new parameter semantics, 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 verb ('List') and resource ('WooCommerce merchants participating in the KaliCart Global federated catalog'), and specifies the return fields (domain, storefront URL, product count). While it doesn't explicitly contrast with siblings like lookup_merchant, the usage hint ('Use before global_search') implies a distinct role in discoverability.
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 before global_search to understand catalog coverage.' This indicates when to invoke it relative to another tool. No exclusions or alternative recommendations are given, but for a simple listing tool this is sufficient 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: 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.