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

Annotations already mark this as a safe read-only tool, and the description adds genuine behavioral context: weekly snapshot cadence, default filtering of reimbursement placeholder SKUs, and the summary-vs-issues content difference. It stops short of describing pagination or result shape, but the cadence and filtering notes are real value beyond 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?

Front-loads the core purpose and view semantics before the alternative-tool guidance. The sentences are dense but each carries information; the closing alternative-fan-out sentence is longer but earns its place by preventing misuse.

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, return values need not be explained, and the description covers the view modes, default filtering, and freshness cadence well for a complex 16-parameter tool. Minor gaps remain around pagination behavior, which the schema's offset description partly covers.

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 schema already documents all 16 parameters including view, severity, and the view-scoped filters. The description restates the two view meanings but adds no syntax or format detail beyond the schema, making the 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?

States a specific verb and resource ('Return weekly Listings Items API quality snapshots') and immediately distinguishes its two view modes, giving an agent a clear sense of what it produces versus sibling listing 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?

Explicitly states the alternative path: for a live buyability check, fan out across get_buybox_status, get_listing_restrictions, and get_fba_eligibility, and cross-reference get_suppressed_listings. This correctly routes the agent away from this weekly-snapshot tool when live data is needed.

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