Get Product Details

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

Annotations already indicate a read-only, idempotent operation, but the description adds valuable context: it details the return fields, explains the 'N/A' sentinel, notes USD currency, and describes error handling for missing API key and invalid ASINs. This goes beyond the annotation baseline.

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 well-structured with clear sections (Returns, Prices, Args, Examples, Error handling) and is front-loaded with the primary purpose. It is slightly long due to repeating schema info for the 'Args' section, but every section serves a useful role, so it earns a 4.

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?

Despite having no output schema, the description thoroughly enumerates the return fields, clarifies value semantics, and covers error scenarios. For a simple 2-param tool, this is complete enough for an agent to correctly select and invoke the tool.

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% for both asin and domain, so the schema already provides parameter meaning. The description repeats the asin argument and domain default without adding new semantic detail beyond a couple of examples, which is marginal value. 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?

The description clearly states the tool fetches current product details for a given Amazon ASIN, naming the specific resource (Keepa product data) and scope (current snapshot). It distinguishes itself from sibling tools like get_price_history and get_best_sellers by focusing on current details and listing the exact returned fields.

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?

Examples provide concrete use cases ('What is the current price...') and imply when to use this tool, but it does not explicitly contrast with alternatives like get_price_history for historical data. The description gives clear contextual guidance without formal exclusions, so it earns a 4 rather than 5.

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