amazon_search: GET /

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.