keepa_batch_product_lookup

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

No annotations are provided, so the description carries the full burden. 'Look up information' implies a read operation, but it does not disclose any details such as whether price history is included by default, what 'information' includes, or any constraints beyond the ASIN count. This is a minimal but not transparent description for a data retrieval tool.

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 a single, concise sentence that front-loads the core purpose and includes a key constraint (up to 100). There is no redundant or filler content.

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 tool's simplicity and the fact that the schema fully explains parameters, the description is sufficient for an agent to understand the tool's function. It differentiates from the singular product lookup sibling and includes the batch limit. A lack of return-format guidance is acceptable since no output schema exists and the description needn't explain return values.

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%, with all four parameters (days, asins, domain, history) having clear descriptions. The tool description itself adds no parameter-level detail beyond what the schema provides, so a baseline score of 3 is appropriate.

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 ('Look up') and resource ('Amazon products by ASIN') and clearly differentiates from sibling keepa_product_lookup by emphasizing 'multiple' and 'up to 100'. This makes the purpose unmistakable.

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 implies when to use this tool: when you need to look up multiple products at once (up to 100). However, it does not explicitly mention alternatives or when not to use it (e.g., for a single ASIN, use keepa_product_lookup), leaving usage guidance implicit rather than explicit.

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