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

Annotations already declare readOnly/idempotent/non-destructive/no-open-world, so the safety profile is covered. The description adds genuinely useful context: it is a paged bulk scan (pages of 100 offers, not one call per offer) and returns examples plus handling-time outliers, which signals cost and result shape 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?

One dense but well front-loaded sentence: the '[Analysis]' tag and the bulk-scan scope come first, followed by the measured dimensions and the routing guidance. Slightly run-on, but every clause carries information.

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 there is no need to describe return values, and the description nonetheless covers scope, sampling strategy, defaults, and when to choose it over per-offer reads. An agent has everything needed to invoke it correctly.

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% and both parameters are documented there (account from list_accounts, max_pages default). The description's 'pages of 100 offers' and 'enough for 2000 offers' restates the schema's semantics rather than adding new meaning, so the baseline 3 applies.

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 (audit/analysis) and resource (whole catalog) and enumerates exactly what it measures: active/rejected/out-of-stock offers, missing EAN, missing buy button, handling time outliers. This clearly separates it from per-offer siblings like offers_get and offers_list.

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 says to use it 'for any question about the whole catalog instead of reading offers one by one', giving both the selection condition and the alternative it replaces. An agent knows to pick this over looping offers_list.

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