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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful context beyond that: cross-retailer support, the Amazon-specific ASIN mode, and the concrete set of returned fields. There is no contradiction with the annotations.

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 concise sentences plus one illustrative example. The purpose, key constraints, and supported retailers are front-loaded, and every sentence earns its place without redundancy.

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?

Even without an output schema, the description names the returned fields and the example plus schema cover the valid call patterns. It does not discuss error cases, rate limits, or exact response types, but for a simple read-only product detail tool this is a minor gap.

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 coverage is 100%, so the schema already documents every parameter well. The description reinforces the url-vs-id relationship and provides an example, but it does not add meaningfully new semantics beyond what the input schema and its examples already convey.

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 clearly states that the tool retrieves product detail from named retailers and lists the returned fields (title, brand, price, rating, availability). It does not explicitly contrast itself with siblings like unwrangle_reviews or unwrangle_search, so it stops just short of full sibling differentiation.

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 provides concrete input-mode guidance: pass a URL for any retailer, or an Amazon id/asin for Amazon. However, it never explicitly says when to prefer unwrangle_product over unwrangle_search or unwrangle_reviews, leaving the comparative usage context implied rather than stated.

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