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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond that: it returns match rows, an interpretation of the natural-language sentence, and facet counts, and it explains that prices carry both a billed amount and an estimated USD/month figure. It says nothing about pagination limits, result-size caps or rate limits.

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 that front-load the search scope and then the return shape, with no filler. The trailing attribution line ('Served by r4ck…') is boilerplate but minimal, so it costs little.

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?

For a 26-parameter, no-output-schema tool the description does well to describe the response shape (rows, parse interpretation, facets) and the price normalization. It is still thin for the filter matrix: an agent must open the schema to learn paging behavior, sort semantics, and how broad region/country filters combine with spec filters.

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 26 parameters and only 58% schema description coverage, roughly half the fields are undocumented in structured form. The description explains the natural-language 'q' behavior (the sentence is interpreted and reflected back) and clarifies the USD-per-month basis of price filters, which partly compensates for the min_price/max_price gap, but it says nothing about sort/order defaults, offset/limit paging, or the interplay among the many enum filters.

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 every offer') plus the dimensions searched ('by spec, price and place'), so an agent knows this is the broad listing/search endpoint. It does not distinguish itself from siblings like r4ck_cheapest, r4ck_deals or r4ck_facets, so it stops short of a 5.

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 description says what the tool returns and that facet counts support 'narrowing', which implies an exploratory-search use case, but it never states when to prefer this over r4ck_cheapest, r4ck_deals, r4ck_facets or r4ck_parse_query. No exclusions, prerequisites or fallback guidance are given.

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