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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuine context beyond that: it is a free-text search and it returns id, title and address. It stops short of describing result volume, pagination, or ordering, which are the remaining unknowns for a search tool.

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 front-loaded sentence that opens with the action and then supplies scope and return fields. It is slightly overstuffed with nested parentheticals and duplicates the market definitions that the schema already carries, which is wasted effort for an agent that reads both.

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 two-parameter read tool with no output schema, the description usefully names the return fields, which offsets the missing output schema. However, it omits how results are ranked or capped and how it relates to the similarly named sibling 'search_models', leaving real gaps for an agent choosing between them.

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 coverage is 50%: 'market' is fully documented in the schema (and the description merely repeats it, earning no extra credit), while 'query' has no schema description at all. The description partially compensates by labelling the query as free text, but it adds no detail on matching behavior, syntax, or what an empty/ambiguous query does.

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 the fridges in FridgeBase's comparison') plus the two supported markets and the fields returned (id, title, address). It is clear what the tool does, but it never distinguishes itself from the sibling 'search_models', so an agent cannot tell the two apart from the description alone.

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?

Implies usage via 'free text' and the market enum, so an agent knows it is a keyword search over the fridge catalog. There is no explicit when-to-use guidance, no statement of when to prefer 'search_models' or 'get_model' instead, and no mention of prerequisites or result limits.

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