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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description still adds real behavior beyond them: results are candidates only, no live pricing is returned, and the slug is the key to hand to the next tool. Pagination/ordering behavior is not mentioned, keeping it below a 5.

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?

Four short sentences, front-loaded with purpose, then the call-order rule, then the negative constraint. No filler, and the brand caveat is a single trailing clause.

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 no output schema, the description still characterizes the return well enough for an agent: a list of candidate slugs, not live prices, and how to consume a slug downstream. Nothing needed to call this two-parameter read-only search correctly is missing.

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 100%, so the schema already documents 'q' and 'limit' including the default 8 / max 20. The description's only extra signal is that a candidate's answer slug (or EAN) feeds get_unit_price's answer parameter; it adds nothing about search-text syntax or limit behavior.

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?

Names a specific verb and resource (search Slovak Cite Q&A slugs on nakus.sk) and adds concrete domain examples (diapers, laundry, pet food, coffee). It also explicitly distinguishes itself from the sibling tools by stating what it does NOT return (live €/unit).

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?

Gives an explicit ordering rule ('Use FIRST when you do not know the exact answer slug or EAN'), names the next tool to call ('get_unit_price with answer=<slug>') and routes card-only requests to get_price_card after a slug exists. When-to-use, when-not-to-use and alternatives are all covered.

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