find_cheapest

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

No annotations are provided, so the description carries the full burden, and it does well: it discloses the hit-selection heuristic (first of top 3 with usable shop offers, else first hit), that non-selected hits surface as alternatives, and that refurbished offers are excluded but counted in refurbished_hidden. It omits auth/permission or rate-limit context, which are lower priority here.

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-loaded with the primary action, then selection behavior, then the refurbished caveat; nearly every clause carries information. It is dense but readable, with only mild sentence-length pressure in the second sentence.

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-value documentation is not required, and the description instead covers the non-obvious selection and filtering behavior well. The one gap is offer_limit semantics, which leaves an agent guessing about a tunable that changes the result.

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%, so the description must carry parameter meaning. It explains include_refurbished thoroughly and explains the semantics of the query search, but offer_limit is never mentioned — the agent cannot tell whether it caps returned offers, offers-per-product, or something else.

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 for a product and return the best match plus its cheapest offers. The phrase 'in one call' signals that it is a composite of the sibling search/specs/offers tools, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied ('find cheapest offers for a product') and there is a genuine when-not constraint for include_refurbished ('only set that when the user explicitly asks for refurbished/outlet items'). However it never says when to prefer this over search_products, get_product, or get_cheapest_offers, so the agent must infer routing.

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