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

Annotations only cover the safety profile (readOnly/openWorld/non-destructive); the description adds substantive traits beyond that: Amazon rate limits (~1 batch of 20 every 10s), the 'all-in for the customer' semantics of buy_box_price, and the reason field values for missing Buy Box (suppressed / no offers). This is exactly the extra context annotations do not supply.

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?

Front-loads READ-ONLY, then what it returns, then the intended use, then the rate-limit caveat, then the alternative. Dense but every clause carries signal; nothing is filler despite the length.

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?

There is no output schema, so the description carries the return-value burden and does so by naming the per-ASIN fields and the no-Buy-Box reason. Combined with rate-limit disclosure and the execute_sql alternative, an agent has everything needed to call it correctly and avoid misuse.

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%, so asins (max 100), account_id, and customer_type are already documented in the schema; the description largely restates the 100-ASIN limit. It adds little semantic detail for account_id/customer_type, so the baseline 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?

States a specific verb and resource ('BULK Buy Box / Featured Offer export for a LIST of ASINs') plus scope (up to 100). It also enumerates return fields (buy_box_price, lowest_price, offer_count, win flag, FBA/FBM, no-Buy-Box reason), making it clearly distinguishable from siblings like get_my_pricing, get_competitive_pricing, or reprice_to_buybox.

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?

Gives the triggering intent verbatim ('give me the Buy Box price for these ASINs' / export) and an explicit when-not: do NOT loop this for the whole own catalog; instead query the cached fact_buybox_snapshot via execute_sql. Both the alternative and the condition selecting it are named.

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