search_products

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

No annotations are provided, so the description must carry behavioral disclosure. It discloses the per-store result cap behavior (max_results per store) and language support (English or Hebrew), which is useful. However, it doesn't describe pagination, result ordering, permission requirements, or error behavior for a multi-store query.

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?

Front-loaded one-line summary followed by compact per-parameter notes. No filler; each sentence serves a purpose.

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 3-param query tool with an output schema, the description covers the key non-obvious semantics (language, store examples, default, per-store cap). Missing only error/permission behavior and ordering, which are secondary given an output schema exists.

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 0%, so the description must compensate. It documents query (language support) and stores (example store names) and max_results (default and per-store semantics). It adds real value on stores and max_results semantics, but does not fully document the type-contract for query or the enumeration of valid store names.

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 clear verb (search) and resource (products) with a scope qualifier (across all or selected grocery stores). Distinguishes itself from cart/recipe siblings but not explicitly from compare_prices, which is a related but different action.

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 implies usage through the store-limiter and per-store cap, but doesn't state when to use this versus compare_prices or plan_recipe_ingredients. No explicit exclusions or alternative routing.

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