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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the lower bar applies; the description still adds real value by disclosing pagination limits (25 per page, 10 pages per query) and what each offer carries (per-case and per-unit prices in the offer's own currency, pack, duty status, Incoterm, location, stock). It omits error behavior and whether results are ranked or ordered.

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?

Three tightly packed sentences: scope first, return contents second, pagination constraints last. No filler, though the return-contents sentence is list-heavy and could be trimmed given an output schema exists.

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?

An output schema exists so return values need only brief mention, and pagination limits are explicitly given, which is the main operational risk. Some gaps remain around filter combination behavior and the undefined enum values (stock_status, incoterm), but the definition is sufficient to call the tool 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?

With 11 parameters at 55% schema coverage, the description adds useful meaning by giving size/pack examples ('70cl', '6x70cl') and clarifying that currency is per-offer rather than a filter-only concern. However, it leaves several parameters (brand exact-match, origin, location, stock_status, incoterm semantics, page bounds) to the schema or undocumented, so it only partially compensates for the coverage gap.

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 (search open akay.ie trade offers) and enumerates the search axes plus optional filters, so an agent knows exactly what corpus is queried. It does not differentiate itself from the sibling 'search' tool, leaving some ambiguity about which search variant to pick.

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?

The word 'open' implies closed/expired offers are excluded, and the searchable facets hint at how to query, but there is no explicit when-to-use guidance and no routing to alternatives such as get_offer, list_categories or the generic 'search'. Usage is implied rather than stated.

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