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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds substantive behavioral context beyond them: data provenance preference for Catalog Items with fallback to Listings Items quality or seller active-listings data, and the default filtering of reimbursement placeholder SKUs. This discloses non-obvious behavior an agent would otherwise miss.

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 paragraph is front-loaded with the view semantics followed by data-source and filtering notes. It is efficient overall, though the view definitions partially duplicate the schema's enum descriptions, which is minor 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?

With an output schema present and annotations covering the safety profile, the description needn't explain return values, and it covers views, provenance, and default filtering adequately for a 15-parameter tool. The only gap is the absence of guidance on how it relates to the many sibling listing/catalog tools.

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 baseline is 3 and the schema already documents every parameter, including the view enum and the include_synthetic_skus default. The description restates the view meanings and the reimbursement-filter behavior rather than adding format or interaction detail the schema lacks.

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 gives a precise verb+resource and enumerates exactly what each of the three views returns (ASIN/SKU rows, searchable/sortable rows, resolved brand ASIN set), so an agent knows the scope without opening the schema. It does not, however, differentiate from siblings like get_listing_quality, get_offer_listings, or get_suppressed_listings, which also touch listing data.

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 clearly states when each view applies ('search' discovers or sorts by text or creation date; 'brand_asins' resolves active ASINs for a catalog brand), which is real routing guidance. It stops short of naming when to choose this tool over the neighboring listing/product tools or any exclusions.

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