list_manufacturersList vetted Ukrainian manufacturers from the Gemalli marketplace. Returns localised name, country, certifications, and per-locale slug for the first N published profiles, ordered by recency. For text + country search, use Wave 3b auth tools.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1–50). Defaults to 12. | |
| locale | No | Preferred locale for returned text. Defaults to "en". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses a read-only listing behavior (non-destructive), returns only 'published profiles' with a limit, orders by recency, and states the returned attributes. It does not mention authentication or rate limits, but for a simple list operation the disclosed behavior is adequate.
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 with no wasted words. The purpose and return info are front-loaded, and the routing guidance is a natural second sentence. Efficient and well-structured.
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 two-parameter list tool with no output schema and no annotations, the description adequately covers what it returns, ordering, limit behavior, and the alternative search path. It lacks explicit notes on authentication or error conditions, but these are minor for a read-only list operation, so it is nearly 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 both parameters, giving a baseline of 3. The description adds value by linking 'limit' to 'first N published profiles' and 'locale' to 'localised name' and 'per-locale slug', clarifying how the parameters affect output beyond the schema descriptions.
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 states a specific verb ('List') and a resource ('vetted Ukrainian manufacturers from the Gemalli marketplace'), and details the return fields (localised name, country, certifications, per-locale slug). However, it does not explicitly differentiate from siblings like get_manufacturer or search_products, so it lacks explicit sibling distinction.
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?
The description explicitly provides an alternative condition: 'For text + country search, use Wave 3b auth tools.' This tells the agent when not to use this tool and routes to an appropriate alternative, satisfying the 'when-not' guidance clearly.
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 maps to a distinct resource and action: product/manufacturer retrieval, catalog search, category listing, HS classification, dual-use screening, sanctions screening, and partnership inquiry. The compliance checks are related but clearly separated by HS-code vs. name-based screening, so an agent is unlikely to pick the wrong tool.
Most tools follow a predictable verb_noun snake_case pattern: check_, get_, list_, search_, lookup_. partnership_inquiry is the only clear deviation, using a noun phrase instead of a verb-led name, but the overall convention is still easy to infer.
Nine tools is a well-scoped size for a public B2B trade and compliance server. Each tool covers a distinct step in the catalog-discovery or pre-flight workflow, with no redundant or decorative entries.
The core workflows are covered: category browsing, product search, manufacturer retrieval, HS classification, dual-use and sanctions screening, and partnership outreach. A minor gap is the lack of direct manufacturer text/country search, which is explicitly deferred to separate Wave 3b auth tools; agents can still discover manufacturers indirectly through product search.