Rechercher des produits

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

Annotations already provide read-only and safe-behavior hints. The description adds return format details but does not disclose further behavioral traits. It does not contradict annotations.

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 and front-loaded with the purpose. However, the Args section redundantly repeats schema information, wasting some space.

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 coverage and informative annotations, the description is mostly complete. However, it lacks details on keyword matching behavior and the exact fields returned, which would be helpful without an output 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?

Schema coverage is 100%, but the description contains a factual error: it states pageSize default 20 and max 100, while schema says default 30 and max 500. This misleads the agent, reducing the value beyond 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 products by keywords with pagination, using specific verbs and resource. It distinguishes from sibling tools like 'boond_products_get' which retrieves a single product.

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 searching products by keywords but does not explicitly mention when to use versus alternatives like 'boond_products_get'. No exclusions or alternative tools are referenced.

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