run_amazon_product_offers

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

With no annotations, the description carries the full burden. It usefully discloses a billing trait ('Flat 5 points per successful run') and implies a read-only scope via 'Get', but says nothing about pagination, whether 'all' offers are truly complete, rate limits, or auth needs. Partial disclosure earns a middle score.

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?

Two tight sentences with zero filler; the core capability and returned fields are front-loaded, and the cost note is a compact, useful second sentence.

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?

For a two-parameter read tool with no output schema, the description helpfully enumerates the returned fields (price, condition, seller, delivery), which compensates for the missing output schema. It is slightly incomplete in not acknowledging the domain parameter's effect on which marketplace is queried.

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 the ASIN and domain parameters are already documented in the schema; baseline is 3. The description mentions the ASIN key but adds no meaning about the multi-domain enum or what changing domain implies for results.

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 (Get) and resource (all marketplace offers for an Amazon product) plus the identifying key (ASIN) and the fields returned. An agent can distinguish it from run_amazon_product and run_amazon_seller_products, though it does not name those siblings explicitly to reinforce the distinction.

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 never says when to reach for this tool versus the many adjacent Amazon tools (run_amazon_product, run_amazon_seller_products, run_amazon_product_search). There is no when-to-use, prerequisite, or exclusion guidance; the agent must infer routing from the name alone.

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