Rechercher des produits

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint, so the safety profile is clear. The description adds pagination and return info, but no further behavioral traits such as rate limits or scope limitations. No contradictions with 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 brief, structured with Args and Returns, and front-loaded with the main purpose. The inaccuracies reduce its value, but structurally it's clean.

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 100% schema coverage and helpful annotations, the description's incorrect defaults and missing 'fields' parameter make it incomplete and potentially misleading. An agent relying on the description might pass wrong pageSize values or overlook the fields projection option.

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?

The description omits the 'fields' parameter entirely and states incorrect defaults for pageSize (says 20/max 100, while schema says default 30/max 500). This actively misleads the agent and undermines the schema's accuracy. With 100% schema coverage, the description should align with the schema or add value; instead it contradicts it.

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 a specific verb and resource. It distinguishes from sibling tools like boond_products_get (which retrieves a specific product) by emphasizing keyword-based search.

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 clearly indicates when to use this tool (search products by keywords) and includes pagination context. It doesn't explicitly list exclusions or alternatives, but the 'search' role is clear, and sibling tools like get/create/update/delete are distinct.

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