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

Annotations already cover read-only and non-destructive behavior, so the description should add operational context such as pagination, filter combination semantics, or what 'policy and history' actually dictate. It only restates the domain ('independently verified') without disclosing how results are produced, ordered, or limited. No contradiction with 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?

The description is a single sentence with no filler, and the verb and object are front-loaded as 'Filter independently verified offers'. It is efficiently compact, though the brevity sacrifices substantive detail.

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 9 parameters, no output schema, and only safety annotations provided, the description is too thin to support correct invocation. It does not explain the response shape, default limit behavior, cursor usage, or how 'policy and history' translate into concrete filter arguments.

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 0% for 9 parameters, and the description's phrase 'by policy and history' does not map to any specific parameters like evidenceRequirements, minimumVerifiedCompletions, or network. The agent is left to guess which of the 9 fields correspond to 'policy' vs 'history' and how they interact.

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 uses a specific verb ('Filter') with a clear resource ('independently verified offers') and states selection criteria ('by policy and history'). The term 'independently verified' helps position the tool against general offer commerce tools, though it does not explicitly distinguish it from sibling tools like get_verified_offer or discover_assurance_services.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention get_verified_offer for single-offer lookup, discover_assurance_services for broader scanning, or any context triggers or exclusions; an agent must infer usage entirely from the tool name.

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