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

Beyond the readOnly/openWorld annotations, the description discloses important behavior: this is a pure data fetch with no AI analysis, history is returned 'when available', money is in the marketplace's local currency, and calling without a marketplace fetches nothing and answers 'MARKETPLACE NEEDED'. This gives the agent accurate expectations about failure modes and result semantics.

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 front-loaded with the core purpose and output contents, then gives a concrete usage workflow)Skip? The text is dense and mostly earns its sentences, but it is a long single paragraph and repeats marketplace details already present in the schema, so it is not maximally tight.

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?

With no output schema, the description adequately communicates the major returned data categories and how to interpret them for a sourcing decision. It also covers the marketplace prerequisite and the no-data failure mode. It does not enumerate exact fields or response shape, but for a two-parameter fetch tool this is sufficiently complete.

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?

Both parameters already have detailed schema descriptions, and the input schema explicitly explains the marketplace's ask-once/reuse behavior, the no-US-assumption rule, the 'MARKETPLACE NEEDED' failure mode, and currency. The main description largely repeats that marketplace guidance rather than adding new semantic meaning, so the high schema coverage makes a baseline 3 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 names a concrete, scoped operation: fetching full raw data for a single Amazon product by ASINca, and it lists the data categories included (price, estimated sales/revenue, reviews, rating, listing quality, sellers, history). The phrase 'single product by ASIN' and 'pure data fetch (no AI analysis)' clearly separate it from siblings like analyze_niche, analyze_product_set, and compare_products.

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?

It gives explicit usage context: audit the product like a sourcing analyst, evaluate demand, pricing, competition, and listing quality, then produce GO/NO-GO. It also prescribes the marketplace workflow precisely: ask once if no marketplace is named, reuse it for later calls, and do not assume the US. It does not explicitly name alternative tools or state when not to use this one, so it falls short of a 5.

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