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

Beyond the read-only/idempotent annotations, the description discloses deduplication, concurrent fetching, per-ASIN billing including not-found results, the 413 limit beyond 20 ASINs, the multi-variant listing caveat for bullets/specs, and the meaning of null fields. This is far more behavioral transparency than annotations alone provide.

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?

Every sentence carries distinct operational value: batch identity, concurrency, cost, billing edge case, limit behavior, data caveat, and null-field interpretation. The description is compact relative to the amount of behavior it discloses and front-loads the most important facts.

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, combined with the detailed schema and annotations, covers what the tool does, when to use it, its limits, its costs, edge-case behaviors, and returned-field semantics. With an output schema present, return-value details are already handled, so no meaningful operational gap remains.

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%, so the baseline is 3; the description adds meaningful semantics by explaining deduplication and the 20-ASIN maximum, the not-found billing consequence, and the semantic caveat that bullets/specs may describe the product family rather than the exact variant. This enriches the parameter meaning without contradicting the schema.

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 states a specific verb and resource: 'Batch variant of product_details', 'Accepts a comma-separated ASIN list... fetches all of them concurrently.' It clearly differentiates itself from product_details and other siblings by focusing on the batch ASIN capability rather than reviews, sellers, or offers.

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 gives clear context: use this batch variant when you need multiple ASINs, and it is 'far cheaper and faster than N single calls.' It names product_details as the base variant, implying single-ASIN use is routed there, though it does not explicitly state when-not or list alternative tools for overlapping needs.

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