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

Annotations already mark the tool as non-read-only, non-destructive, and open-world; the description adds that it is live/on-demand and scoped to one ASIN per call. It does not disclose other behavioral traits such as latency, invalid-ASIN handling, or any side effects, but given the annotation coverage, the bar is lower and the description adds reasonable context.

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: it front-loads the core capability and return values, then provides usage guidance and examples, then closes with scope and cardinality. Every sentence earns its place, and the examples are concrete without bloating the text.

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 tool has no output schema, so the description compensates by summarizing the return payload: current price, offers, sellers, brand, title, price range, and fulfillment. It also covers marketplace support and the one-ASIN-per-call constraint. It stops short of specifying exact response shape or edge-case behavior, but for a two-parameter live-lookup tool the coverage is strong.

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 both 'asin' and 'marketplace_id' are already documented in the input schema. The description restates that one ASIN is used and that all marketplaces are supported, but it does not add meaningfully new parameter-level details beyond the schema. 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?

The description uses a specific verb-resource pair ('Pull a LIVE, on-demand snapshot of a single Amazon ASIN') and enumerates what is returned: current title, price, live offers, and sellers. It also distinguishes itself from the 'pre-collected dataset,' making it clear this is the real-time alternative to other data-lookup tools.

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 explicitly states when to use the tool: 'Use when the user gives a specific ASIN and wants its CURRENT/today's data rather than the pre-collected dataset,' with concrete example queries. It does not name an alternative sibling tool, but the contrast with pre-collected data supplies a clear selection rule, so it stops just short of full alternative-name guidance.

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