search_products

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

With no annotations, the description must disclose behavioral traits. It reveals that results are grouped by chain and include normalized price, unit price, size, and promotion info. It also implies parallel search across chains. However, it does not explicitly state read-only behavior or potential latency.

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?

The description is concise at three sentences, with the main action front-loaded. Every sentence adds useful information without redundancy. It efficiently covers the tool's scope, examples, and result structure.

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?

Given the lack of an output schema, the description adequately describes the return format (grouped by chain with price, unit price, size, promotion info). It covers key features but omits details on pagination behavior or error handling, which are partially in the schema.

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?

Although schema coverage is 100%, the description adds value by providing example queries for the 'query' parameter, clarifying that omitting 'chains' searches all, and giving concrete examples for filters (maxPrice, sizeRange). This enhances understanding beyond the schema.

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?

The description clearly states the tool's purpose: searching for products across configured Swiss grocery chains by keyword. It lists the specific chains and mentions optional filters, making it distinct from sibling tools like get_product (single product) or find_stock (stock search).

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 provides concrete example queries ('find organic milk under 2 CHF', 'compare pasta prices') that illustrate when to use the tool. It also implies when to use it vs. siblings, but does not explicitly state exclusions or alternatives.

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