Amazon Remote MCP Server

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: delivery-zone-aware pricing when a zip/location is set, and the fact that the other-sellers block only appears when otherSellers=true. It omits the credit cost (that lives only in the schema) and any rate-limit or failure behavior.

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 purpose sentence is front-loaded and the alternative/conditional notes come after. The long enumerated list of return fields and the use-case tail make the second paragraph dense, but since no output schema exists the field enumeration is largely earning its place.

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, the description usefully enumerates the returned fields (price, Buy Box seller, variants, offers block) and covers the main conditional behaviors, making it callable with confidence. It leaves out cost/credit implications for the extra request and any pagination or error handling, which are minor for a single-item fetch.

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, but the description goes further by tying parameters to outcomes — the otherSellers=true flag producing the other-sellers offers block and the zip/location inputs enabling zone-aware pricing. That conditional linkage adds meaning beyond the flat field 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 and resource ('Fetches a single Amazon product page by ASIN') plus the domain scope, which cleanly separates it from the sibling tools that fetch reviews, search results, or seller data. An agent can identify the tool's job 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?

It names concrete scenarios (price/stock monitoring, catalog enrichment, listing QA, Buy Box tracking, cross-locale analysis) and flags the conditional otherSellers=true path, giving clear context for when to reach for it. It stops short of explicit exclusions or naming a sibling to prefer instead, so it does not reach a 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?

Annotations already establish readOnlyHint=true and destructiveHint=false, and the description usefully adds that the fetch is paginated and enumerates the returned fields (title, body, stars, author, media URLs, rating histogram). It omits page-size limits, rate limits, and auth requirements, so it is above baseline but not exhaustive.

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?

It is front-loaded with the action and scope before diving into filter and return-value detail, and the two sentences map well onto the tool's two concerns. The second sentence is quite dense and partly padding ('feeding review-summarization or Q&A agents'), but overall it earns its length for a 10-parameter tool.

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, the description correctly compensates by enumerating the returned review fields and the aggregate rating histogram, and it discloses pagination coverage. It lacks details on page-size behavior, maximum pages, or rate limiting, which are the remaining gaps for a network-bound external fetch.

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% and 7 of 10 parameters are enums, so the schema already documents filter semantics fully. The description restates the filter families (star rating, reviewer type, media-only, format, keyword, sort) but adds no syntax, defaults, or interaction detail beyond the structured fields, so the baseline of 3 applies.

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 names a specific verb and resource ('Get Amazon Product Reviews') and immediately scopes it to a single Amazon ASIN, which cleanly separates it from the sibling tools dealing with product details, search results, and sellers. An agent can identify the resource and granularity 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?

It lists concrete use cases (voice-of-customer analysis, sentiment extraction, competitor benchmarking, review-summarization agents) that make the intended context explicit. However, it never names an alternative tool or a condition under which a different sibling (e.g. product details) should be preferred, so routing guidance is incomplete.

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?

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds real context beyond them: the returned fields (ASIN, price, list price, Prime/sponsored flags, position), pagination behavior, and location/zip scoping. It does not mention auth requirements, rate limits, or result caps, which keeps it short of a 5.

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?

Front-loads the purpose in the first sentence and the return shape in the second, with no filler. The second sentence is dense with field enumerations but each clause carries information; only slight trimming would improve it.

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, the description correctly compensates by listing the returned fields, and it covers pagination, sorting, and location scoping for a seven-parameter tool. Auth/permission and result-limit details are absent, but for a read-only public search endpoint the definition is otherwise sufficient to invoke 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?

Schema description coverage is 100%, so all seven parameters are already documented in the schema, including enums for domain, sortBy, and language. The description restates the sort options in human-readable form and mentions delivery scoping, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (keyword search) and resource (Amazon results on a chosen domain) and enumerates the scope knobs (pagination, delivery location, sort order). The sibling set is all product/review/seller detail lookups, so the search-SERP framing clearly distinguishes this tool from 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?

Explicitly lists usage contexts: SERP monitoring, share-of-shelf tracking, competitor discovery, ASIN harvesting to feed the product/reviews endpoints, and price-comparison agents. The mention of feeding downstream product/reviews endpoints implicitly routes the agent away from this tool for detail lookups, but no explicit when-not-to-use statement is given.

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds useful behavioral context by characterizing the profile as 'public' and enumerating the returned fields (ratings breakdown, feedback counts, address, contact, customer service), though it omits auth requirements, rate limits, and pagination.

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?

Front-loads the verb and resource, then supplies return detail and use cases in a logical order with no filler. The opening line duplicates the title, and the return-field inventory plus five-item use-case list push length, but each element is informative.

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, the enumerated return fields replace what an output schema would normally provide, and the annotations cover the safety profile. Three parameters at 100% coverage leaves nothing material about calling the tool unexplained.

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% and both enums (domain, language) are self-documented with defaults and constraints. The description only restates sellerId and the domain/language selection, adding no format, range, or dependency detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Fetches') and resource ('public storefront profile for an Amazon seller') and identifies the key ('by sellerId') plus scope ('chosen domain/language'). This is clearly distinguishable from siblings like getProductDetails, getProductReviews, and getSellerProducts, so an agent can route without opening schemas.

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?

Gives concrete when-to-use scenarios (due-diligence/vetting, brand protection, MAP-violation investigations, leaderboards, directory enrichment), which is strong context. However, it never states when not to use it or names the natural alternative (getSellerProducts for listing a seller's catalog), leaving that inference to the agent.

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond them by disclosing pagination behavior and enumerating the returned row fields (ASIN, title, image, URL, price/list price, currency, rating, review count). It omits auth/prerequisite and rate-limit details, keeping it from a 5.

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 core scoping sentence is front-loaded and dense with useful detail, and the use-case list is compact. The opening 'Get Amazon Seller Products' restates the title rather than adding information, which is minor waste but slightly dilutes an otherwise efficient structure.

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, the description correctly compensates by enumerating return fields, and it covers pagination and the domain/seller scoping. It does not explain how pagination terminates (total pages/next page) or output envelope, which would help since no output schema exists.

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 page, domain, language, and sellerId are all documented in the schema with enums for domain and language. The description only echoes sellerId and 'chosen domain' without adding format, default, or interaction detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource (paginated listing of a seller's storefront catalog by sellerId/domain) and distinguishes it from neighbors by pointing to the product and reviews endpoints for per-ASIN drill-downs. An agent can tell it apart from getSellerDetails, getProductDetails, and getSearchResults without opening any 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?

Gives explicit usage contexts (mapping a competitor's assortment, detecting SKU launches, building watchlists, price-intelligence, seeding deep-dives) and names the sibling endpoints for follow-up. It stops short of stating when NOT to use it (e.g., single-product or keyword lookups), so it is clear context rather than full when/when-not routing.

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