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

Annotations already declare read-only, idempotent and non-destructive behavior. The description adds useful context beyond annotations by describing the return fields (id, title, url, snippet) and the follow-up workflow to 'fetch'.

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 compact sentences front-loaded with the action and scope. The final connector note is brief and helps routing without padding.

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 an output schema and safety annotations, the description is nearly complete. The main missing element is routing guidance against the sibling 'search_products'.

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% and documents both parameters, so the baseline is 3. The description adds that the free-text query accepts Croatian or English, a constraint not stated in the schema, though it adds no extra detail for max_results.

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 ('Search') and resource ('Svijet Beba product catalog'), including product types and query languages. It distinguishes itself from 'fetch' by routing full-detail requests there, but never addresses the sibling 'search_products'.

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?

Provides clear context by calling itself a generic entry point and tells the agent to pass returned IDs to 'fetch' for details. It lacks explicit when-not conditions or a comparison to the similar sibling 'search_products'.

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