amazon_search

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

No annotations are provided, so the description carries the full burden. It adds some behavioral context by listing product attributes returned (price, rating, review count, ASIN), but does not explicitly state read-only semantics, pagination, or potential response structure. The word 'Search' suggests read-only, but more disclosure would be better.

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 concise sentences, front-loaded with purpose. The second sentence reinforces the Amazon-specific use case, adding relevance for sibling differentiation without redundancy.

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?

The description provides purpose and some output field details, while the schema covers all parameters with clear descriptions. There is no output schema, so the returned fields hint helps. Minor gaps like response envelope or error handling are typical for a search tool, but it is sufficiently complete for an agent to select and invoke.

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?

The input schema provides 100% coverage with descriptions for all four parameters, including defaults and constraints. The description adds no parameter-level meaning beyond the schema, 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 clearly states the tool searches Amazon for products and lists key output fields (price, rating, review count, ASIN). It distinguishes from siblings by explicitly targeting Amazon, which differentiates it from google_shopping and other general search 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?

It says 'Use this for e-commerce product lookups on Amazon specifically', providing clear context for when to use. However, it does not explicitly name alternatives or state exclusion cases, so it stops short of a full 5.

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