search_products

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

With no annotations, the description only adds that prices are in main currency units (e.g., 1500 = GBP 1,500). It omits other behavioral traits such as result format, pagination, cross-seller search, or sorting behavior.

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 sentences with no fluff. First sentence states purpose, second adds an important price clarification. Efficient and well-structured.

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?

Despite 14 parameters and no output schema, the description is very sparse. It lacks high-level guidance on category formats, result count, sorting, or how to combine filters effectively. Incomplete for a complex search tool.

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 coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema, only repeating 'category and optional filters' and the price note. No extra semantic guidance on parameter usage.

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 the Merka2a marketplace for products, using a category and optional filters. This distinguishes it from sibling tools like get_product (single product) or browse_categories (category discovery).

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?

It mentions providing a category and filters, but does not explicitly state when to use this tool versus alternatives like browse_categories or get_product. No guidance on prerequisites or exclusions.

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