Search products

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

No annotations are provided, so the description carries the burden. It discloses the return of matches with ids and prices, and hints at language behavior (Catalan works best). However, it does not discuss edge cases (e.g., empty results), pagination, or sorting. Adequate but not exhaustive.

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?

Description is two sentences, no waste. The first sentence states purpose and dependency, the second adds usage guidance. All content earns its place.

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 no output schema, the description explains return values (ids and prices) and dependency (needed for add_to_cart). For a simple two-parameter search tool, this is nearly complete. Missing details like sorting or scope of search, but not critical.

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 parameters are already documented. The description adds extra meaning: advice on query length and language ('short term; Catalan works best'), which is not in the schema. This helps the agent formulate better queries.

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?

Description clearly states the tool finds a product and its id, which is needed before adding to cart. The verb 'find' and resource 'product' are specific, and it distinguishes itself from sibling tools like ametller_get_product (which retrieves by id) and ametller_add_to_cart (which uses the id).

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?

Description indicates when to use the tool (before ametller_add_to_cart) and provides practical tips: use short terms, Catalan works best, examples given. While it doesn't explicitly state when not to use it, the context is clear within the sibling set.

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