amazon_search: GET /

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

With no annotations, the description transparently covers the read-only nature, pagination, supported sort orders, delivery location scoping, and the structure of returned data. However, it omits details on rate limits, data freshness, or authentication requirements.

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 concise, covering functionality, parameters, returns, and use cases in a single paragraph. It is front-loaded and each sentence adds value, though it could be structured with bullet points for clarity.

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?

Given no output schema, the description provides a detailed list of return fields and mentions related suggestions and facets. It is sufficient for understanding the tool’s role in product research and price comparison, though it lacks explicit mention of the response format.

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% and the description adds little beyond listing parameters like 'domain' and 'sortBy'. It contextualizes their role in filtering and sorting but does not significantly extend the schema 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 clearly states the tool performs a keyword search on Amazon domains with pagination, delivery scoping, and sort options. It enumerates return fields (ASIN, title, price, etc.) and lists concrete use cases like SERP monitoring and competitor discovery, distinguishing it from siblings such as product details or reviews.

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 cases are provided but no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or contrast with sibling tools like product details or seller details, leaving the agent to infer based on return fields.

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