amazon_product: GET /

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It mentions that otherSellers=true triggers extra data extraction and that deliveryZip/shippingLocation affect pricing. It does not cover rate limits or auth, but for a read-only product lookup, this is adequate.

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 moderately sized with a clear title and structured sentences. It front-loads the core purpose and then lists return fields and use cases. A bit verbose in listing all return fields, but still efficient overall.

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 the lack of an output schema, the description provides a comprehensive list of return fields (title, brand, price, availability, etc.) and covers behavior for optional parameters (otherSellers, delivery zip/location). It is complete for an agent to understand what the tool does and what to expect.

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?

All 6 parameters are described in the schema (100% coverage). The description adds context beyond the schema: it explains the role of otherSellers (triggering other sellers block) and notes that deliveryZip and shippingLocation enable delivery-zone-aware pricing. This adds meaningful value.

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 explicitly states it fetches a single Amazon product page by ASIN on a chosen domain, and lists the extensive data returned. It clearly distinguishes itself from sibling tools like search, reviews, and seller details.

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?

The description enumerates specific use cases such as product research, price/stock monitoring, catalog enrichment, listing QA, Buy Box tracking, and cross-locale analysis. It does not explicitly state when not to use or mention alternatives, but the context is clear enough for an agent to infer appropriate usage.

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