Check whether the user is allowed to sell (ungated for) one or more ASINs on their Amazon account. Call for 'am I ungated for this?' or 'can I sell these ASINs?'. Returns per-ASIN {state, gated, apply_link}. Uncached ASINs are queued for a fresh check, so re-call shortly for any still pending. Requires a connected Amazon account.
| Name | Required | Description | Default |
|---|---|---|---|
| asins | Yes | ||
| condition | No | new_new |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses caching behavior (uncached ASINs queued, re-call needed), return structure (state, gated, apply_link), and prerequisite (connected Amazon account). It doesn't mention side effects or rate limits, but the tool is read-only by nature.
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 four sentences, each adding value: purpose, usage example, behavior/return, and prerequisite. No fluff, front-loaded with the main action.
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?
Without an output schema, the description covers the return shape and async behavior well. However, it omits details about the 'condition' parameter and its possible values, which is a gap for a complete understanding.
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 0%, so the description must explain parameters. It explains 'asins' (array of ASINs to check) but does not mention the 'condition' parameter (with default 'new_new') at all, leaving a significant gap.
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 checks if a user is ungated for ASINs, provides example queries, and mentions return fields. It distinguishes itself from sibling tools which are mostly get/dashboard functions, none of which check eligibility.
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 gives specific example use cases ('am I ungated?', 'can I sell these ASINs?') and notes the caching behavior requiring re-call for pending ASINs. It doesn't explicitly state when not to use, but the context is clear and no alternative tool exists among siblings.
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.
