Profitable online-arbitrage (OA) deals: retail products matched to Amazon listings with profit and ROI. Call when the user asks about OA or retail sourcing opportunities. sort: roi, profit, price, newest, sell, rank, monthly_sold or sellers.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| sort | No | roi | |
| search | No | ||
| min_roi | No | ||
| max_rank | No | ||
| per_page | No | ||
| retailer | No | ||
| min_profit | No | ||
| min_monthly_sold | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It fails to mention pagination (page, per_page), result limits, read-only nature, or any side effects. The description is too brief for a tool with 9 parameters and no output schema.
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?
The description is two short sentences plus a list of sort options. It is front-loaded, begins with the core purpose, and contains no redundant text. Every sentence serves a clear function.
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 the tool's complexity (9 parameters, no output schema, 0% schema description coverage), the description is inadequate. It does not cover filtering, pagination, or response structure, leaving significant gaps for an agent to use the tool correctly.
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?
The description lists possible values for the 'sort' parameter, which adds value beyond the schema. However, with 0% schema description coverage and 8 other parameters (page, search, min_roi, etc.) completely unmentioned, the description does not compensate sufficiently. Most parameters remain unexplained.
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 returns profitable OA deals, retail products matched to Amazon listings with profit and ROI. It specifies the context ('OA or retail sourcing opportunities') and lists sort options, effectively distinguishing it from siblings like get_oa_retailers.
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?
Explicit guidance: 'Call when the user asks about OA or retail sourcing opportunities.' This provides clear when-to-use context. However, it does not mention when not to use or suggest alternatives, which would improve the score.
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 targets a distinct data type or action (e.g., product analysis, deal types, FBA operations). Even similar-sounding tools like get_deal_results and get_oa_deals are clearly separated by domain (A2A vs OA) in descriptions. No significant overlap.
All tools follow a clear verb_noun pattern with underscores (e.g., analyse_product, create_deal_task, get_credits). The consistent 'get_' prefix for retrieval tools and varied but predictable action verbs make the set easy to navigate.
At 37 tools, the set is large but covers a broad Amazon seller ecosystem (research, sourcing, FBA, deals, monitoring). Each tool serves a distinct purpose, and the count reflects the domain's complexity without being bloated.
The tool surface covers all major seller workflows: product analysis, profit calculation, sourcing, deal discovery, storefront monitoring, FBA operations, purchase tracking, price alerts, and reconciliation. No obvious gaps for core tasks.
