Amazon Pricing

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that requests are proxied through the Decodo Web Scraping API and that output is parsed JSON, which is useful context, but says nothing about pagination behavior (pageFrom exists), latency, or how an empty offers list appears.

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?

Three compact sentences: action and return format first, use case second, doc link last. Nothing is wasted, though the docs URL and the API-target parenthetical are somewhat promotional rather than operational.

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 5 parameters, no output schema, and a 100%-described schema, the description covers purpose and return type but not the returned offer structure (price, seller, condition, shipping) an agent needs before consuming the JSON. It is adequate to invoke, but incomplete for interpreting results.

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 every parameter (geo, query, domain, jsRender, pageFrom) is already documented in the schema. The description only restates that query is an ASIN and adds no syntax, default, or interaction details (e.g., how geo and domain combine). Baseline 3 is correct here.

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 (Fetch) and resource (offers for an Amazon product identified by ASIN), plus the transport layer (Decodo Web Scraping API `amazon_pricing` target) and the response shape (parsed JSON). An agent can distinguish it from amazon_product or amazon_sellers by the stated 'offers / what different sellers charge' framing, though no sibling is named explicitly.

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 one positive use case: 'compare what different sellers charge for the same product'. There is no explicit when-not guidance, no mention of when to prefer amazon_product or amazon_sellers instead, and no prerequisites stated. Usage is implied rather than specified.

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