Amazon Search

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds useful context that results come from a live scraping API and are returned as parsed JSON, implying real-time fetching, but says nothing about latency, credit cost, rate limits, or failure modes when scraping is blocked.

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?

Two sentences: purpose first, then usage, with the docs link last where it belongs. No padding, though the docs URL could arguably be trimmed in favor of inline caveats.

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?

No output schema exists, and the description does state the return shape (product listings parsed as JSON). For a scoped, low-parameter search tool this is nearly sufficient, with only pagination behavior and result-emptiness handling left unmentioned.

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 five parameters (geo, query, domain, jsRender, pageFrom) are already documented in the schema. The description only echoes the keyword and domain concept, adding no format or interaction guidance (e.g., how geo interacts with domain). 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 (search) and resource (Amazon product listings), plus the mechanism (Decodo Web Scraping API `amazon_search` target) and return type (JSON). The Amazon qualifier distinguishes it from walmart_search/target_search, but it doesn't explicitly distinguish itself from amazon_bestsellers or amazon_product, which also return Amazon product data.

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?

"Use it to find products and compare listings on a chosen Amazon domain" gives implied usage context, but there are no exclusions or alternatives named. An agent must infer that amazon_product is for a single ASIN and amazon_bestsellers for ranked lists rather than keyword search.

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