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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: live SP-API freshness ('right now') and the semantic meaning of an empty offer_count. It does not discuss rate limits or truncation behavior, which the schema only hints at.

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?

Three sentences, front-loaded with the core purpose before the return fields and the usage signal. Efficient with no filler; it could tighten slightly but every sentence carries information.

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?

An output schema exists, so return values need not be spelled out, yet the description still frames them usefully. Annotations carry the safety profile and the schema covers all parameters, leaving little an agent needs that is missing.

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 all five parameters (asin, customer_type, item_condition, include_raw_rows, include_diagnostics) are already documented in structured form. The description adds no syntax or default guidance beyond what the schema provides, which is the correct baseline when the schema does the heavy lifting.

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 ('See who is selling a product right now') and enumerates the returned fields (seller IDs, pricing, fulfillment method, feedback, Buy Box). Scope is sharpened by 'live SP-API'. It does not, however, differentiate itself from the similarly named sibling get_listing_offers, leaving ambiguity an agent must resolve.

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 an explicit consumption signal ('offer_count == 0 as a buyability signal') and names three complementary tools (get_buybox_status, get_listing_restrictions, get_fba_eligibility). What it omits is when to pick this over get_listing_offers, the closest sibling, so routing is only partially solved.

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