search_products

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

No annotations are provided, so the description must carry the full burden. It mentions output includes price summaries and retailer prices, but does not disclose pagination behavior, whether searches are across all retailers, or if results are real-time. More transparency would be beneficial.

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?

Two concise sentences with no wasted words. The first sentence states the action and input, the second states output. Perfectly front-loaded and efficient.

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 full schema parameter descriptions, no output schema, and moderate complexity, the description is mostly complete. It could mention pagination behavior or that it searches across all retailers, but it's not critically 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?

All 5 parameters have schema descriptions, so baseline is 3. The description adds value by clarifying the query parameter accepts Greek or English text, and mentions outputs that give context to sortBy options (price, unit_price). This goes 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 searches PosoKanei supermarket products by Greek or English text, and returns price summaries and retailer prices. This verb+resource+scope combination distinguishes it from siblings like get_product (single product) and lookup_barcode (by barcode).

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 for text-based product search, but does not explicitly state when to use this tool vs alternatives (e.g., list_products_by_category for category browsing, lookup_barcode for barcode input). No exclusions or prerequisites are mentioned.

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