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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: it pages through the marketplace internally, the returned count covers every match regardless of the row limit, and each result is a matching offer. It stops short of describing error behavior or what happens when max_pages is exhausted.

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: purpose and filter inventory first, then the routing rule. The parenthetical about Vendwiser paging is slightly intrusive but earns its place by explaining why one call suffices.

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?

Output schema exists, so return values need no prose, and the filter set is well covered. Minor gaps remain around account selection when multiple accounts are connected and what happens if matches exceed the page scan budget — both partially addressed by the schema.

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?

With only 36% schema description coverage across 14 parameters, the description carries much of the burden — it names nearly every filter dimension (name words, SKU prefix, status, price/stock range, handling time, validation state, buy button lost, campaign membership) and clarifies that name matching is word-based. It doesn't explain the interplay between limit and max_pages, which is left to the schema.

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 ("Find offers"), the scope ("across the WHOLE catalog in one call"), and enumerates the exact filter dimensions supported. It is clearly distinguishable from offers_list (paging) and offers_get (single offer).

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 routes the agent: "Use this instead of paging offers_list whenever the question is about which or how many offers match something." The alternative tool and the condition that selects it are both named, which is the strongest form of guidance.

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