Amazon Remote MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It reveals that otherSellers triggers an extra request and 5-credit cost, that shipping parameters enable delivery-zone-aware pricing, and enumerates the returned data fields. This goes beyond a simple fetch statement and sets accurate expectations.

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 longer than minimal, but each sentence earns its place: purpose, return fields, conditional behavior, and use cases. The dense field list is justified because no output schema is present, making the enumeration valuable rather than filler.

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 and no annotations, the description fully compensates by enumerating the core returned data, covering conditional behaviors like otherSellers and shipping-location pricing, and listing relevant use cases. Nothing essential for an agent to decide when and how to call this tool is missing.

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%, providing a baseline of 3. The description adds meaningful semantics beyond the schema by explaining the otherSellers cost/extra-request tradeoff, how deliveryZip/shippingLocation affect pricing, and domain/language dependencies. This supplements the parameter definitions without redundancy.

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 opens with a specific verb and resource: 'Fetches a single Amazon product page by ASIN on a chosen Amazon domain.' This clearly distinguishes product details from sibling tools focused on reviews, search, and seller data, even without naming them.

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?

Lists concrete use cases including product research, price/stock monitoring, listing QA, Buy Box tracking, and cross-locale analysis. This gives clear context for when to use the tool, though it does not explicitly state when not to use it or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses pagination ('Paginated fetch'), the filtering dimensions, and enumerates the returned per-review fields plus aggregate rating histogram. It does not mention rate limits, authentication needs, or error behavior, but for a read-only GET tool the disclosed behavior is substantial and useful.

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 efficient and front-loaded: the first sentence states the action, the next sentence lists filters, then outputs, then use cases. The use-case enumeration is slightly longer than strictly necessary but earns its place for agent selection. No redundancy or tautology.

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?

With no output schema and 10 parameters, the description compensates well by enumerating both the filter capabilities and the exact return fields, including the aggregate histogram. It lacks explicit default values for page, sortBy, or mediaType and does not describe response pagination metadata, but these are minor gaps given the rich input/output description present.

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%, so the baseline is 3. The description adds value beyond the schema by clarifying the semantics of several enum-based filters: 'star rating (1-5, positive, critical)' maps to stars, 'current-variant vs all-formats' clarifies format, and 'media-only reviews' clarifies mediaType. This helps an agent choose parameter values without needing to infer from enum names alone.

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 opens with a specific verb and resource ('Get Amazon Product Reviews') and immediately expands to 'Paginated fetch of customer reviews for an Amazon ASIN,' clearly distinguishing it from the sibling tools that handle product details, search, and seller data. The scope is unmistakable even without opening the schema.

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 provides clear usage context by listing concrete use cases: voice-of-customer analysis, sentiment extraction, feature-request mining, competitor benchmarking, and review summarization. It does not explicitly exclude alternatives like getProductDetails or search_getSearchResults, but the distinct resource type makes the intended use obvious, so it earns a 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and largely succeeds: it discloses that results are organic, that sponsored/Prime flags and position are included, and that related search suggestions and filter facets are returned. It omits error/rate-limit caveats and slightly mislabels sort values, but the behavioral details are substantial.

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 organized into three purposeful sentences: action, return payload, and use cases. The opening phrase 'Get Amazon Search Results' is slightly redundant with the tool name, but the rest is dense and front-loaded.

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 tool with 7 parameters, no annotations, and no output schema, the description covers the operation, scoping options, return fields, and downstream applications well. It is not fully complete because pagination mechanics and exact sort-value naming are left ambiguous, and sibling-tool routing is only implied.

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%, so the baseline is 3. The description adds human-readable meaning for sort order and delivery zip/location scoping beyond the schema, though it does not fully reconcile its sort wording with the schema enum (e.g., 'newest' vs 'newestArrivals' and the omitted 'bestSellers').

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 uses a specific verb ('Runs a keyword search') and identifies the resource (a chosen Amazon domain), then details the returned data. This makes it unmistakably distinct from the sibling product-details, reviews, and seller 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?

Concrete use cases are listed: SERP monitoring, share-of-shelf tracking, competitor discovery, ASIN harvesting to feed downstream product/reviews endpoints, and product-research/price-comparison agents. It gives clear context for when to use this tool, though it does not explicitly say when to prefer a sibling tool instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. It clearly indicates a non-destructive read of public data ('Fetches the public storefront profile') and enumerates return content. It does not discuss rate limits, failure modes, or authentication, but 'public' and 'fetches' make the core behavior 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?

The body is front-loaded with the core operation, followed by useful return-content and use-case context. The heading line 'Get Amazon Seller Details' duplicates the tool name, and the use-case list is slightly long, but there is no true filler.

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 read-only look-up with 3 parameters and no output schema, the description is complete: it identifies what is returned, the required identifier, the domain/language context, and the use cases that justify selecting the tool. No critical selection or invocation information is missing.

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%, so the schema already documents sellerId, domain, and language. The description adds only that the fetch is 'by sellerId on the chosen domain/language,' which maps to the parameters but does not add new semantic detail beyond the 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?

The description states a specific operation — fetches the public storefront profile for an Amazon seller by sellerId on a domain/language — and names the resource (seller profile) and scope. It is clearly distinct from sibling tools focused on product details, reviews, search results, or seller product listings.

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?

It gives explicit use cases (seller due-diligence, vetting, counterfeit/brand-protection, MAP-violation investigations, leaderboards, seller-directory enrichment), so an agent knows the intended context. It does not explicitly say when NOT to use it or name an alternative tool, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states the listing is paginated and lists the exact fields returned per product row. It does not mention rate limits, page size, or explicit read-only status, but for a GET listing endpoint the disclosed behavior is reasonably 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?

The description is moderately concise and front-loaded with the core operation. The opening phrase 'Get Amazon Seller Products' is redundant with the tool name, but the following sentence quickly explains the paginated catalog behavior. The use-case list is slightly long but still relevant.

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?

Since there is no output schema, the description usefully enumerates the expected return fields and notes pagination. It does not mention page size, sorting, or language-domain dependency behavior, but those are partially covered by the input schema and are not critical for this moderate-complexity listing 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 description coverage is 100%, so the schema already explains page, domain, language, and sellerId. The description adds contextual framing around sellerId and domain but no additional parameter-level syntax or constraints beyond what the schema provides.

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 defines a specific operation: a paginated listing of a seller's storefront catalog for a given sellerId and domain. It also enumerates the returned fields, making it easy to distinguish from the sibling tools such as getSellerDetails, getProductDetails, and getSearchResults.

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 provides concrete use cases such as mapping a competitor's assortment, detecting new SKU launches, and building brand-protection watchlists. It also hints at downstream deep-dives against product and reviews endpoints, but it does not explicitly state when not to use this tool or name alternative tools as direct conditionals.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.