List a merchant's in-stock products (product_id, title, price, availability, url). Call after find_merchant to see the catalogue, then get_product for full detail. For a specific shopper need, prefer search_products.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max products to return (default 50, max 200). | |
| merchant | Yes | Agenticfeed merchant ID (customer GUID), e.g. "a9a8378c94". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, but description discloses that it returns in-stock products with specific fields and implies read-only behavior. Missing details on auth or rate limits, but overall transparent.
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 efficient sentences, front-loaded with purpose, 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?
Given no output schema, description lists returned fields. Covers purpose, usage context, and data details adequately for a list 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?
Schema coverage is 100% with good descriptions. Description adds contextual usage order but no additional parameter-specific meaning beyond 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?
Description clearly states 'List a merchant's in-stock products', specifying verb and resource, and differentiates from siblings by mentioning call order and alternative tools.
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 says when to use: after find_merchant, before get_product, and when to prefer search_products. Provides clear workflow 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.